[Tickets #14368] Re: Improve EAS performance with large History tables

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14368
------------------------------------------------------------------------------
  Ticket             | 14368
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Improve EAS performance with large History tables
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2016-05-25 12:46) wrote:


> Our MySQL server uses the history_action index, but even if I force  
> MySQL to use the object_uid index it's still over 1 second. The  
> moqseq 956528 is from April 2015. I hoped there is a way to prevent  
> checking the same history entries every 15 seconds for a year, at  
> least in these cases when a user doesn't use a collection.

What about adding a composite index on history_action, object_uid?  
Since mysql uses the index that returns the least number of rows, this  
should improve performance when the modseq range is extremely high.