zookeeper-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [zookeeper] enixon commented on issue #905: ZOOKEEPER-3359: Batch commits in the CommitProcessor
Date Mon, 03 Jun 2019 23:02:24 GMT
enixon commented on issue #905:  ZOOKEEPER-3359: Batch commits in the CommitProcessor 
URL: https://github.com/apache/zookeeper/pull/905#issuecomment-498457278
 
 
   Some numbers:
   
   I set up a basic ensemble of five peers and ran a job that created 2k mutations per second
and 2k reads per second on that ensemble. While I'm (afaik) prohibited from sharing exact
numbers, I can share relative numbers.
   
   Tests were run with with configuration A as the defaults (1 write per batch and no read
batching) and with configuration B using both read and write batches set to 10 (-Dzookeeper.commitProcessor.maxCommitBatchSize=10
-Dzookeeper.commitProcessor.maxReadBatchSize=10).
   
   The max time that both reads and writes spend in the commit processor queue is reduced
by 30% when moving from A to B (so B is 70% of A) and similarly for the max time that reads
and writes spend in the system entirely. We also see more stable, lower metrics recorded for
time writes spend in the final request processor. Averages improve even more dramatically
with both reads and writes moving through the commit processor (and the system entirely) in
35% the time under B that they did under A.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message