Details
-
Sub-task
-
Status: Open
-
Critical
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Based on performance benchmarks on the clocks, the HybridLogicalClock#now and HybridLogicalClock#update methods are far too costly in multithreaded scenarios especially due to synchronization around the entire methods.
Thus we need an improved implementation of Clock#now and Clock#update such that it would perform better in the presence of multiple threads.