Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

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

Open
Supergirlzjl opened this issue Dec 28, 2024 · 5 comments
Open

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

Supergirlzjl opened this issue Dec 28, 2024 · 5 comments

Comments

@Supergirlzjl
Copy link

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 50,90,95,99,100 --random-data --randomize --distinct-client-seed --hide-histogram --key-minimum 1 --key-maximum 50000000 --key-prefix="type_set_preset_" --command="sadd key data" --command-ratio=1 --command-key-pattern=P -n 500000 -c 1 -t 100 -d 1024 --rate-limiting=200 > /root /logs/sadd-1.log 2>&1 &, the result is as follows
@Supergirlzjl
Copy link
Author 

[RUN #1 100%, 4252 secs] 15 threads:    49907984 ops,   19603 (avg:   11735) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.41) msec latency
[RUN #1 100%, 4252 secs] 15 threads:    49910984 ops,   19603 (avg:   11736) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.41) msec latency
[RUN #1 100%, 4252 secs] 15 threads:    49913984 ops,   19603 (avg:   11736) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49916984 ops,   19603 (avg:   11736) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49919984 ops,   19603 (avg:   11737) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49922984 ops,   19603 (avg:   11737) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49925984 ops,   19603 (avg:   11737) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49928984 ops,   19603 (avg:   11738) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49931984 ops,   19603 (avg:   11738) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49934984 ops,   19603 (avg:   11738) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4254 secs] 15 threads:    49937984 ops,   19603 (avg:   11738) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4254 secs] 15 threads:    49940984 ops,   19603 (avg:   11739) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4254 secs] 15 threads:    49943984 ops,   19603 (avg:   11739) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4254 secs] 15 threads:    49946984 ops,   19603 (avg:   11739) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4254 secs] 15 threads:    49949984 ops,   19603 (avg:   11740) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4254 secs] 15 threads:    49952984 ops,   19603 (avg:   11740) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4254 secs] 15 threads:    49955984 ops,   19603 (avg:   11740) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4255 secs] 15 threads:    49958984 ops,   19603 (avg:   11740) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4255 secs] 15 threads:    49961984 ops,   19603 (avg:   11741) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4255 secs] 15 threads:    49964984 ops,   19603 (avg:   11741) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4255 secs] 15 threads:    49967984 ops,   19603 (avg:   11741) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4255 secs] 15 threads:    49970984 ops,   19603 (avg:   11742) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4255 secs] 15 threads:    49973984 ops,   19603 (avg:   11742) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4256 secs] 15 threads:    49976984 ops,   19603 (avg:   11742) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4256 secs] 15 threads:    49979984 ops,   19603 (avg:   11742) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4256 secs] 15 threads:    49982984 ops,   19603 (avg:   11743) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4256 secs] 15 threads:    49985984 ops,   19603 (avg:   11743) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4256 secs] 15 threads:    49988984 ops,   19603 (avg:   11743) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4256 secs] 14 threads:    49991869 ops,   19603 (avg:   11744) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4256 secs] 12 threads:    49994432 ops,   19603 (avg:   11744) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4256 secs]  8 threads:    49996391 ops,   19603 (avg:   11744) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.39) msec latency
[RUN #1 100%, 4257 secs]  6 threads:    49997820 ops,   19603 (avg:   11744) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.39) msec latency
[RUN #1 100%, 4257 secs]  5 threads:    49998980 ops,   19603 (avg:   11744) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.39) msec latency
[RUN #1 100%, 4257 secs]  2 threads:    49999564 ops,   19603 (avg:   11744) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.39) msec latency
[RUN #1 100%, 4257 secs]  1 threads:    49999777 ops,   19603 (avg:   11744) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.39) msec latency
[RUN #1 100%, 4257 secs]  1 threads:    49999977 ops,   19603 (avg:   11744) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.39) msec latency
[RUN #1 100%, 4257 secs]  0 threads:    50000000 ops,   19603 (avg:   11744) ops/sec, 20.40MB/sec (avg: 12.22MB/sec),  2.89 (avg:  6.39) msec latency

100       Threads
1         Connections per thread
500000    Requests per client


ALL STATS
============================================================================================================================================================
Type         Ops/sec    MOVED/sec      ASK/sec    Avg. Latency     p50 Latency     p90 Latency     p95 Latency     p99 Latency    p100 Latency       KB/sec 
------------------------------------------------------------------------------------------------------------------------------------------------------------
Lpushs      11364.63         0.00         0.00         6.39472         3.18300         6.77500         7.65500        12.42300    557842.43100     12108.22 
Totals      11364.63         0.00         0.00         6.39472         3.18300         6.77500         7.65500        12.42300    557842.43100     24216.43

@Supergirlzjl Supergirlzjl mentioned this issue Dec 28, 2024
Closed
@Supergirlzjl
Copy link
Author 

nohup memtier_benchmark -s 10.71.**.80 -p 6379 -a 1234** --cluster-mode --print-percentiles 50,90,95,99,100 --random-data --randomize --distinct-client-seed --hide-histogram --key-minimum 1 --key-maximum 50000000 --key-prefix="type_set_preset_" --command="sadd __key__ __data__" --command-ratio=1 --command-key-pattern=P -n 500000 -c 1 -t 100 -d 1024 --rate-limiting=200  > /root /logs/sadd-1.log 2>&1 &

@YaacovHazan
Copy link
Collaborator

Hi @Supergirlzjl not sure I understand. Do you refer to the fact that memtier-benchmark printing several lines with 100%?

@Supergirlzjl Supergirlzjl closed this as not planned Won't fix, can't repro, duplicate, stale Dec 30, 2024
@Supergirlzjl
Copy link
Author

Hi @Supergirlzjl not sure I understand. Do you refer to the fact that memtier-benchmark printing several lines with 100%?

Yes, this is one of the questions. Another question is that repeated data is printed for some time, as shown below. In addition, I saw in the redis monitoring that the actual end time of the stress test is inconsistent with the time calculated through the log (4257 secs). Therefore, I suspect that the log printing is confused for some reason?

[RUN #1 100%, 4253 secs] 15 threads:    49916984 ops,   19603 (avg:   11736) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49919984 ops,   19603 (avg:   11737) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49922984 ops,   19603 (avg:   11737) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49925984 ops,   19603 (avg:   11737) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49928984 ops,   19603 (avg:   11738) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency
[RUN #1 100%, 4253 secs] 15 threads:    49931984 ops,   19603 (avg:   11738) ops/sec, 20.40MB/sec (avg: 12.21MB/sec),  2.89 (avg:  6.40) msec latency

@Supergirlzjl
Copy link
Author

Sorry, I closed this issue by mistake.

@Supergirlzjl Supergirlzjl reopened this Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@YaacovHazan @Supergirlzjl