memtier_benchmark

memtier_benchmark copied to clipboard

`:latest` Docker tag out of date - `--rate-limiting` flag not yet published to "stable" image

3

At the time of writing (9/24/2024), the `--rate-limiting` flag introduced by PR #237 has not yet been built and released to the official memtier Docker image `redislabs/memtier_benchmark:latest`, even though it...

DrEsteban

startup error ：void shard_connection::push_req(request*):Assertion 'm_request_per_cur_interval > 0 ' failed

1

When we use the --rate-limiting parameter in the 2.1.2 version of memtier_benchmark, the following error is occasionally reported when starting. I don't know if it is related to the size...

Supergirlzjl

mustansirali

CPU util wouldn't go above 40% on numa node1

1

Here is the command I'm using to start the memcached instance: numactl -N 0 --membind=0 memcached -p 11211 -l 127.0.0.1 -t 128 -u nobody -m 1000000 -c 9999 -d numactl...

montagetao

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...

Supergirlzjl

fix ``

kikitux

It is not reasonable that the latency data includes the time for benchmark generation. Can we add some optimization to remove the time for benchmark data generation from the latency...

Supergirlzjl

When using memtier_benchmark version 2.1.2, a bug occurs where duplicate logs and incorrect data are occasionally printed.

5

Using memtier_benchmark version 2.1.2, there is a bug of repeated log printing and incorrect data: The command is as follows: nohup memtier_benchmark -s 10.71.**.80 -p 6379 -a 1234** --cluster-mode --print-percentiles...

Supergirlzjl