[OAK-4732] (Slightly) prioritise reads over writes

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.7.4, 1.8.0
• Component/s: segment-tar
• Labels: Performance scalability
• Epic Link: TarMK transaction rate
• Assignee: Andrei Dulceanu
• Reporter: Michael Dürig
• Created: 31/Aug/16 16:23
• Updated: 04/Oct/19 17:49
• Resolved: 06/Jul/17 09:19

Description

When fetching the current root from the SegmentNodeStore an older revision will be returned when a commit is being processed concurrently. I think it would make sense to wait for a short time in this case increasing the chance of returning an up to date state. The idea is that this would lower the rebasing work that need to be done later on should the returned root be used for further modifications.

An interesting value for the wait time is to use the median (or more general a percentile) of the commit time of the last say 1000 commits. This would mean that (for the median) we have a 50% chance of getting up to date date. For a 90% percentile we would have longer wait times but then a 90% chance of getting up to date date.

Issue Links

• breaks: OAK-6430 Remove Apache Commons Math3 dependency from Segment Tar
• depends upon: OAK-4122 Replace the commit semaphore in the segment node store with a scheduler
• is related to: OAK-6483 Segment-based composite node store performance degradation
• relates to: OAK-6428 Add flag for controlling percentile of commit time used in scheduler