You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the backfill function is very verbose printing each key that is inserted to stdout or (in this case) to the catalina.out file while the writeSingle function just prints the summary with WPS. I wonder if this is the reason why the backfill is able to reach just 40k wps thorughput while writes are over 100k wps.
The text was updated successfully, but these errors were encountered:
For some odd reason the throughput for the backfill function is much lower then for writes. I'm using the same concurrency.
Test was conducted with the following setup:
application.properties has following:
ndbench.config.numKeys=250000000
ndbench.config.writeRateLimit=400000
ndbench.config.readRateLimit=500000
ndbench.config.numValues=50000
ndbench.config.dataSize=1024
ndbench.config.numWriters=1000
ndbench.config.numReaders=1000
ndbench.config.backfillStartKey=1
ndbench.config.numBackfill=1000
ndbench.config.cass.host=172.31.31.228
ndbench.config.cass.keyspace=ndbench
ndbench.config.cass.cfname=scylla
ndbench.config.cass.cluster=NDBench
ndbench.config.cass.colsPerRow=6
ndbench.config.cass.writeConsistencyLevel=ONE
ndbench.config.cass.readConsistencyLevel=ONE
ndbench.config.cass.connections=32
I noticed that the backfill function is very verbose printing each key that is inserted to stdout or (in this case) to the catalina.out file while the writeSingle function just prints the summary with WPS. I wonder if this is the reason why the backfill is able to reach just 40k wps thorughput while writes are over 100k wps.
The text was updated successfully, but these errors were encountered: