Skip to content

When the speed limit parameter value is small, the startup error is reported #303

@Supergirlzjl

Description

@Supergirlzjl

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?

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions