Skip to content

Fix mem reqs #213

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

Merged
merged 3 commits into from
Feb 12, 2023
Merged

Fix mem reqs #213

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e38cc57
fixed for memtier_benchmark-1Mkeys-4KiB-expire-use-case.yml
slice4e Feb 10, 2023
94dbd1e
remove keylen requirement from multi-exec test to prevent it from cr…
slice4e Feb 10, 2023
2426055
fixing memory requiremetns
slice4e Feb 12, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion redis_benchmarks_specification/test-suites/memtier_benchmark-1Mkeys-4KiB-expire-use-case.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ dbconfig:
arguments: '"--data-size" "1000" "--command" "SET __key__ __data__" "--command-key-pattern" "P" "-c" "50" "-t" "2" "--hide-histogram" "--key-minimum" "1"'
resources:
requests:
memory: 1g
memory: 3g
tested-groups:
- string
- generic
Expand Down
4 changes: 2 additions & 2 deletions ...ication/test-suites/memtier_benchmark-1Mkeys-hash-transactions-multi-exec-pipeline-20.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
version: 0.4
name: memtier_benchmark-1Mkeys-hash-transactions-multi-exec-pipeline-20
description: Runs memtier_benchmark, for a keyspace length of 1M keys with a data size of 100 Bytes for each key, focusing on the MULTI EXEC scenario.
description: Runs memtier_benchmark, for a keyspace length of 1M keys with a data size of 100 Bytes for each key, focusing on the MULTI EXEC scenario. TODO - this descriotion needs fixing. We either need a preload command to populate 1M keys, or we need to modify this description.
tested-groups:
- transactions
- hash
Expand All @@ -19,7 +19,7 @@ dbconfig:
configuration-parameters:
save: '""'
check:
keyspacelen: 1000000
keyspacelen: 0
resources:
requests:
memory: 1g
Expand Down
2 changes: 1 addition & 1 deletion ...ks_specification/test-suites/memtier_benchmark-1Mkeys-list-lpop-rpop-with-1KiB-values.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ dbconfig:
arguments: '"--data-size" "1000" --command "LPUSH __key__ __data__" --command-key-pattern="P" --key-minimum=1 --key-maximum 1000000 --test-time 60 -c 50 -t 4 --hide-histogram'
resources:
requests:
memory: 1g
memory: 6g
tested-groups:
- list
tested-commands:
Expand Down
2 changes: 1 addition & 1 deletion ...marks_specification/test-suites/memtier_benchmark-1Mkeys-load-string-with-1KiB-values.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ dbconfig:
keyspacelen: 0
resources:
requests:
memory: 1g
memory: 3g
tested-commands:
- set
redis-topologies:
Expand Down
2 changes: 1 addition & 1 deletion ...chmarks_specification/test-suites/memtier_benchmark-1key-pfadd-4KB-values-pipeline-10.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ dbconfig:
configuration-parameters:
save: '""'
check:
keyspacelen: 1
keyspacelen: 0
resources:
requests:
memory: 2g
Expand Down