Open pveentjer opened 3 years ago
When I add clustering-row-count 1, the problem is resolved.
go/bin/scylla-bench -workload sequential -clustering-row-count 1 -mode write -partition-count 40000 -partition-offset 0 -nodes 172.31.24.133 2>&1 | tee -a scylla-bench-12-08-2021_15-39-25.log
Insertion of 20K is finished super quickly.
So it seems there is roughly a factor of 100 difference between the manually calculated insertion rate and the writes/second listed by Scylla Monitor and scylla-bench. When I add clustering-row-count 1, the problem is resolved.
That's because the default is -clustering-row-count 100
, so 100 rows are inserted for each partition. You get 210 partition inserts per second, which equals to 21000 row inserts per second.
Why not set the default to 1? This makes more sense.
I'm using the following command to insert data:
I can see in Scylla Monitor and on the commandline output that 22K operations/second are done.
So this command should complete in half a second.
But in reality it runs for 46 seconds.
I also calculated the throughput of the inserts manually (so partition-count/time) and I get 210 inserts/second. When I increase to 20K or 30K items, the manually calculated throughput remains constant at 210 inserts/second.
So it seems there is roughly a factor of 100 difference between the manually calculated insertion rate and the writes/second listed by Scylla Monitor and scylla-bench.