[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              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2016-05-27 01:48) wrote:

Ok, this should do it.  If there is a large difference in the last and  
current syncStamp, we now update the state with the new value (only  
implemented in the Sql state driver, not the Mongo driver).

It should be noted that this is only an issue when the client and/or  
user is multiplexing all collections and not using separate  
collections for each calendar/addressbook etc... In that case, the  
modseq is tracked for the individual collection, so there would never  
be that large of a difference in syncstamps unless the client was  
turned off for years....