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
we are running latency focused benchmarks (YCSB Client 0.18.0-SNAPSHOT) with a target throughput and using the measurement.interval=both as described in CHANGES.md
But the reported [Intended-READ] latencies seem to be odd for some databases, resulting in over 100s latencies. See below an example for ScyllaDB (same goes for other tested databases such as Couchbase, PostgreSQL with JBDC, ...)
Hi folks,
we are running latency focused benchmarks (YCSB Client 0.18.0-SNAPSHOT) with a target throughput and using the
measurement.interval=both
as described in CHANGES.mdBut the reported [Intended-READ] latencies seem to be odd for some databases, resulting in over 100s latencies. See below an example for ScyllaDB (same goes for other tested databases such as Couchbase, PostgreSQL with JBDC, ...)
Command line: -db site.ycsb.db.scylla.ScyllaCQLClient -s -p scylla.hosts=100.20.60.80,54.71.135.219,52.26.243.220 -p scylla.keyspace=ycsb -p scylla.username=scylla -p scylla.password=3iaq1MWzBf2AbEv -p scylla.writeconsistencylevel=QUORUM -p scylla.readconsistencylevel=QUORUM -p workload=site.ycsb.workloads.CoreWorkload -p maxexecutiontime=1800 -threads 400 -p recordcount=1000000000 -p operationcount=999900000 -target 117000 -p measurement.interval=both -p fieldcount=10 -p fieldlength=100 -p requestdistribution=uniform -p insertorder=ordered -p readproportion=0.95 -p updateproportion=0.05 -p insertproportion=0.0 -p scanproportion=0.0 -p maxscanlength=1000 -p scanlengthdistribution=uniform -t
Using less threads (10/50/100) results in comparably high latencies for
[Intended-READ]
Running the identical workload (with a lower target throughput) against MongoDB Atlas results in reasonable latencies:
Command line: -db site.ycsb.db.MongoDbClient -s -p mongodb.url=mongodb://root:pCm9YZpSAres@mongodb-m-social-co-shard-00-00.ll86m.mongodb.net:27016,mongodb-m-social-co-shard-00-01.ll86m.mongodb.net:27016,mongodb-m-social-co-shard-00-02.ll86m.mongodb.net:27016,mongodb-m-social-co-shard-01-00.ll86m.mongodb.net:27016,mongodb-m-social-co-shard-01-01.ll86m.mongodb.net:27016,mongodb-m-social-co-shard-01-02.ll86m.mongodb.net:27016,mongodb-m-social-co-shard-02-00.ll86m.mongodb.net:27016,mongodb-m-social-co-shard-02-01.ll86m.mongodb.net:27016,mongodb-m-social-co-shard-02-02.ll86m.mongodb.net:27016/?ssl=true&authSource=admin&maxPoolSize=400&w=majority&j=true&readPreference=primary -p batchsize=1 -p workload=site.ycsb.workloads.CoreWorkload -p maxexecutiontime=1800 -threads 400 -p recordcount=1000000000 -p operationcount=999900000 -target 31000 -p measurement.interval=both -p fieldcount=10 -p fieldlength=100 -p requestdistribution=uniform -p insertorder=ordered -p readproportion=0.95 -p updateproportion=0.05 -p insertproportion=0.0 -p scanproportion=0.0 -p maxscanlength=1000 -p scanlengthdistribution=uniform -t
Any help how to address this issue is much appreciated.
The text was updated successfully, but these errors were encountered: