Affects Version/s: jtsk_1.1
Fix Version/s: None
Bugtraq ID 5026860
All operations on Outrigger's log file are serlialized by a single
lock. Currently each durable operation on a persistent Outrigger will
result in two syncs (we could this down to one, see RIVER-128), this means that
outrigger's overall througput is limited by the cost of these syncs
(e.g. if the two syncs cost 25ms we can only get 40 ops / s).
If we queued up disk ops, and then used a single queue thread to
commit them to disk (while the queuing thread waited on completion of
the commit to disk) when the queue had multiple pending operations we
could write them all out under one set of syncs. This would not
improve the best case latency for durable operations, but should allow
for higher throuput when running multi-threaded work loads.