Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
0.19.0
-
None
-
None
Description
When doing a large number of bulk updates from different clients, I noticed that there was a high level of lock contention for stuff like locking the HLog. It seems that each thread acquires the lock for a single BatchUpdate, releases the lock then another thread owns the lock before the initial writer gets to the next update. Having the threads bounce around may lead to suboptimal performance.
Should be benchmarked & maybe changed to have less context switching.