-
Notifications
You must be signed in to change notification settings - Fork 12
/
Copy pathmemtier_benchmark-1key-zrem-5M-elements-pipeline-1.yml
34 lines (33 loc) · 1.64 KB
/
memtier_benchmark-1key-zrem-5M-elements-pipeline-1.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
version: 0.4
name: memtier_benchmark-1key-zrem-5M-elements-pipeline-1
description: 'Runs memtier_benchmark, for a keyspace length of 1 SORTED SET key. The SORTED SET contains 5M elements and we remove members using ZREM. Throughout the course of the benchmark,the sorted set contains fewer members as we continuously remove them. The chance that we ask for a member to be removed, which was already removed, also increases. Starting with a large number of members helps us to have suffienct number of members for the duration of the benchmark, however the preload stage takes longer to complete. NOTE: using the --randomize flag ensures that we continue to remove elements the longer we run the test. Without the flag, we stop removing elements after some time, possibly we keep generating the same random numbers. '
dbconfig:
configuration-parameters:
save: '""'
check:
keyspacelen: 1
preload_tool:
run_image: redislabs/memtier_benchmark:edge
tool: memtier_benchmark
arguments: --command="ZADD key1 __key__ __key__" --command-key-pattern=P --key-maximum 5000000 --key-prefix "" -n 5000000 --hide-histogram -t 1 -c 1
resources:
requests:
memory: 1g
tested-groups:
- sorted-set
tested-commands:
- zrem
redis-topologies:
- oss-standalone
build-variants:
- gcc:8.5.0-amd64-debian-buster-default
- dockerhub
clientconfig:
run_image: redislabs/memtier_benchmark:edge
tool: memtier_benchmark
arguments: --command="ZREM key1 __key__" --key-maximum 5000000 --command-key-pattern=R --key-prefix "" --hide-histogram --test-time 180 --pipeline 1 -c 1 -t 1 --randomize
resources:
requests:
cpus: '4'
memory: 2g
priority: 36