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

* Your Email Address
* Spam protection	Enter the letters below: . __ .__..__ .__ \| / `[__][ __[__) \|___\__.\| \|[_./\| \
Comment	> >> 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.
Attachment
Watch this ticket