Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backfill function throughput is low. #89

Open
gnumoreno opened this issue Mar 16, 2018 · 0 comments
Open

Backfill function throughput is low. #89

gnumoreno opened this issue Mar 16, 2018 · 0 comments

Comments

@gnumoreno
Copy link
Contributor

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

backfill_load
backfill_throughput

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant