Not an Issue
Details
Details
Assignee
Unassigned
UnassignedReporter
Adrian Phinney
Adrian PhinneyLabels
Components
Affects versions
Priority
Who's Looking?
Open Who's Looking?
Created March 6, 2015 at 2:57 PM
Updated March 9, 2015 at 10:17 PM
Resolved March 9, 2015 at 10:17 PM
Right now, when the timestamp cache is updated it does not account for multiple updates to the same space. This causes multiple unnecessary writes to the second level cache. We have a case where there are ~20 inserts and each causes a timestamp cache put even though the value is the same.
Ideally
PreInvalidate(object[] spaces)
andInvalidate(object[] spaces)
should be changed to acceptISet<string>
likeIsUpToDate()
, but that would be a breaking change.