Prevent updating timestamp cache more than once for the same space

Description

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) and Invalidate(object[] spaces) should be changed to accept ISet<string> like IsUpToDate(), but that would be a breaking change.

Environment

None

Activity

Show:

Alex Zaytsev 
March 9, 2015 at 10:17 PM

Resolved as not an issue as requested

Adrian Phinney 
March 9, 2015 at 8:40 PM

As per my comment on the PR, this can be closeed.

Adrian Phinney 
March 6, 2015 at 3:01 PM

FWIW, this may or may not be considered a bug and also affects NH since this was introduce around 2005.

Adrian Phinney 
March 6, 2015 at 2:57 PM

Not an Issue

Details

Assignee

Reporter

Labels

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
Who's Looking?