We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Test command:
[root@VM-192-20-centos RunnerGo]# memtier_benchmark -s 10.**.13 -p 6379 -a *** --cluster-mode --print-percentiles 50,90,95,99,100 --random-data --randomize --distinct-client-seed --hide-histogram --key-minimum 1 --key-maximum 5000000000 --key-prefix="type_string_write_" --command="set __key__ __data__" --command-key-pattern S --test-time=60 -c 1 -t 10 -d 1024 --rate-limiting=10
Error log:
Writing results to stdout [RUN #1] Preparing benchmark client... [RUN #1] Launching threads now... memtier_benchmark: shard_connection.cpp:357: void shard_connection::push_req(request*): Assertion `m_request_per_cur_interval > 0' failed. Aborted
Can it support low-rate stress testing without reporting errors?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Test command:
[root@VM-192-20-centos RunnerGo]# memtier_benchmark -s 10.**.13 -p 6379 -a *** --cluster-mode --print-percentiles 50,90,95,99,100 --random-data --randomize --distinct-client-seed --hide-histogram --key-minimum 1 --key-maximum 5000000000 --key-prefix="type_string_write_" --command="set __key__ __data__" --command-key-pattern S --test-time=60 -c 1 -t 10 -d 1024 --rate-limiting=10
Error log:
Can it support low-rate stress testing without reporting errors?
The text was updated successfully, but these errors were encountered: