PyPI - redis-benchmarks-specification - Versions diffs - 0.1.291__py3-none-any.whl → 0.1.292__py3-none-any.whl - Mend

redis-benchmarks-specification 0.1.291py3-none-any.whl → 0.1.292py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.

This version of redis-benchmarks-specification might be problematic. Click here for more details.

Files changed (227) hide show

redis_benchmarks_specification/test-suites/memtier_benchmark-1Mkeys-string-setex-100B-pipeline-10.yml CHANGED Viewed

@@ -1,6 +1,7 @@
 version: 0.4
 name: memtier_benchmark-1Mkeys-string-setex-100B-pipeline-10
-description: Runs memtier_benchmark, for a keyspace length of 1M keys with a data size of 100 Bytes for each key.
+description: Runs memtier_benchmark, for a keyspace length of 1M keys with a data
+  size of 100 Bytes for each key.
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -9,10 +10,15 @@ dbconfig:
   preload_tool:
     run_image: redislabs/memtier_benchmark:edge
     tool: memtier_benchmark
-    arguments: '"--data-size" "100" "--ratio" "1:0" "--key-pattern" "P:P" "-c" "50" "-t" "2" "--hide-histogram" "--key-minimum" "1"'
+    arguments: '"--data-size" "100" "--ratio" "1:0" "--key-pattern" "P:P" "-c" "50"
+      "-t" "2" "--hide-histogram" "--key-minimum" "1" "--key-maximum" "1000000" "-n"
+      "allkeys" --pipeline 50'
   resources:
     requests:
       memory: 1g
+  dataset_name: 1Mkeys-string-100B-size
+  dataset_description: This dataset contains 1 million string keys, each with a data
+    size of 100 bytes.
 tested-commands:
 - setex
 redis-topologies:
@@ -23,7 +29,8 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: --test-time 120 --pipeline 10 --command "SETEX __key__ 3600 __value__" --command-key-pattern="R" --key-minimum=1 --key-maximum 1000000 -c 50 -t 4 --hide-histogram
+  arguments: --test-time 120 --pipeline 10 --command "SETEX __key__ 3600 __value__"
+    --command-key-pattern="R" --key-minimum=1 --key-maximum 1000000 -c 50 -t 4 --hide-histogram
   resources:
     requests:
       cpus: '4'

redis_benchmarks_specification/test-suites/memtier_benchmark-1Mkeys-string-setrange-100B-pipeline-10.yml CHANGED Viewed

@@ -1,6 +1,7 @@
 version: 0.4
 name: memtier_benchmark-1Mkeys-string-setrange-100B-pipeline-10
-description: Runs memtier_benchmark, for a keyspace length of 1M keys with a data size of 100 Bytes for each key.
+description: Runs memtier_benchmark, for a keyspace length of 1M keys with a data
+  size of 100 Bytes for each key.
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -9,10 +10,15 @@ dbconfig:
   preload_tool:
     run_image: redislabs/memtier_benchmark:edge
     tool: memtier_benchmark
-    arguments: '"--data-size" "100" "--ratio" "1:0" "--key-pattern" "P:P" "-c" "50" "-t" "2" "--hide-histogram" "--key-minimum" "1"'
+    arguments: '"--data-size" "100" "--ratio" "1:0" "--key-pattern" "P:P" "-c" "50"
+      "-t" "2" "--hide-histogram" "--key-minimum" "1" "--key-maximum" "1000000" "-n"
+      "allkeys" --pipeline 50'
   resources:
     requests:
       memory: 1g
+  dataset_name: 1Mkeys-string-100B-size
+  dataset_description: This dataset contains 1 million string keys, each with a data
+    size of 100 bytes.
 tested-commands:
 - setrange
 redis-topologies:
@@ -23,12 +29,13 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: --test-time 120 --pipeline 10 --data-size-range=1-95 --command "SETRANGE __key__ 5 __data__" --command-key-pattern="R" --key-minimum=1 --key-maximum 1000000 -c 50 -t 4 --hide-histogram
+  arguments: --test-time 120 --pipeline 10 --data-size-range=1-95 --command "SETRANGE
+    __key__ 5 __data__" --command-key-pattern="R" --key-minimum=1 --key-maximum 1000000
+    -c 50 -t 4 --hide-histogram
   resources:
     requests:
       cpus: '4'
       memory: 2g
 tested-groups:
 - string
 priority: 1

redis_benchmarks_specification/test-suites/memtier_benchmark-1Mkeys-string-setrange-100B.yml CHANGED Viewed

@@ -1,6 +1,7 @@
 version: 0.4
 name: memtier_benchmark-1Mkeys-string-setrange-100B
-description: Runs memtier_benchmark, for a keyspace length of 1M keys with a data size of 100 Bytes for each key.
+description: Runs memtier_benchmark, for a keyspace length of 1M keys with a data
+  size of 100 Bytes for each key.
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -9,10 +10,15 @@ dbconfig:
   preload_tool:
     run_image: redislabs/memtier_benchmark:edge
     tool: memtier_benchmark
-    arguments: '"--data-size" "100" "--ratio" "1:0" "--key-pattern" "P:P" "-c" "50" "-t" "2" "--hide-histogram" "--key-minimum" "1"'
+    arguments: '"--data-size" "100" "--ratio" "1:0" "--key-pattern" "P:P" "-c" "50"
+      "-t" "2" "--hide-histogram" "--key-minimum" "1" "--key-maximum" "1000000" "-n"
+      "allkeys" --pipeline 50'
   resources:
     requests:
       memory: 1g
+  dataset_name: 1Mkeys-string-100B-size
+  dataset_description: This dataset contains 1 million string keys, each with a data
+    size of 100 bytes.
 tested-commands:
 - setrange
 redis-topologies:
@@ -23,12 +29,13 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: --test-time 120 --data-size-range=1-95 --command "SETRANGE __key__ 5 __data__" --command-key-pattern="R" --key-minimum=1 --key-maximum 1000000 -c 50 -t 4 --hide-histogram
+  arguments: --test-time 120 --data-size-range=1-95 --command "SETRANGE __key__ 5
+    __data__" --command-key-pattern="R" --key-minimum=1 --key-maximum 1000000 -c 50
+    -t 4 --hide-histogram
   resources:
     requests:
       cpus: '4'
       memory: 2g
 tested-groups:
 - string
 priority: 1

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-100M-bits-bitmap-bitcount.yml CHANGED Viewed

@@ -1,21 +1,28 @@
 version: 0.4
 name: memtier_benchmark-1key-100M-bits-bitmap-bitcount
-description: Runs memtier_benchmark, for a keyspace length of 1 keys focusing on BITCOUNT performance. The bitmap has a size of 100M bits and approximately 2M bits are set. The size of it is ~15MB
+description: Runs memtier_benchmark, for a keyspace length of 1 keys focusing on BITCOUNT
+  performance. The bitmap has a size of 100M bits and approximately 2M bits are set.
+  The size of it is ~15MB
 dbconfig:
   configuration-parameters:
     save: '""'
   check:
     keyspacelen: 1
   init_commands:
-   - '"SETBIT" "users" "100000000" "1"'
+  - '"SETBIT" "users" "100000000" "1"'
   preload_tool:
     run_image: redislabs/memtier_benchmark:edge
     tool: memtier_benchmark
-    arguments: --hide-histogram --command "SETBIT users __key__ 1" --key-maximum 100000000 --key-minimum 1 -n 10000 --key-prefix "" --command-key-pattern R --distinct-client-seed --pipeline 10
+    arguments: --hide-histogram --command "SETBIT users __key__ 1" --key-maximum 100000000
+      --key-minimum 1 -n 10000 --key-prefix "" --command-key-pattern R --distinct-client-seed
+      --pipeline 50
   resources:
     requests:
       cpus: '2'
       memory: 1g
+  dataset_name: 1key-bitmap-100Mbits-15MB-size
+  dataset_description: This dataset contains 1 bitmap key with a size of 100M bits,
+    approximately 2M bits are set, and the total size is around 15MB.
 tested-commands:
 - bitcount
 tested-groups:
@@ -28,10 +35,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: --command "BITCOUNT users __key__ -1" --key-maximum 100000000 --key-minimum 1 --key-prefix "" --command-key-pattern R --distinct-client-seed --test-time 120
+  arguments: --command "BITCOUNT users __key__ -1" --key-maximum 100000000 --key-minimum
+    1 --key-prefix "" --command-key-pattern R --distinct-client-seed --test-time 120
   resources:
     requests:
       cpus: '2'
       memory: 2g
 priority: 19

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-1Billion-bits-bitmap-bitcount.yml CHANGED Viewed

@@ -1,21 +1,28 @@
 version: 0.4
 name: memtier_benchmark-1key-1Billion-bits-bitmap-bitcount
-description: Runs memtier_benchmark, for a keyspace length of 1 keys focusing on BITCOUNT performance. The bitmap has a size of 1 Billion bits and approximately 20M bits are set. The size of it is ~140MB
+description: Runs memtier_benchmark, for a keyspace length of 1 keys focusing on BITCOUNT
+  performance. The bitmap has a size of 1 Billion bits and approximately 20M bits
+  are set. The size of it is ~140MB
 dbconfig:
   configuration-parameters:
     save: '""'
   check:
     keyspacelen: 1
   init_commands:
-   - '"SETBIT" "users" "1000000000" "1"'
+  - '"SETBIT" "users" "1000000000" "1"'
   preload_tool:
     run_image: redislabs/memtier_benchmark:edge
     tool: memtier_benchmark
-    arguments: --hide-histogram --command "SETBIT users __key__ 1" --key-maximum 1000000000 --key-minimum 1 -n 100000 --key-prefix "" --command-key-pattern R --distinct-client-seed --pipeline 10
+    arguments: --hide-histogram --command "SETBIT users __key__ 1" --key-maximum 1000000000
+      --key-minimum 1 -n 100000 --key-prefix "" --command-key-pattern R --distinct-client-seed
+      --pipeline 50
   resources:
     requests:
       cpus: '2'
       memory: 1g
+  dataset_name: 1key-bitmap-1Billion-bits-140MB-size
+  dataset_description: This dataset contains 1 bitmap key with a size of 1 Billion
+    bits, approximately 20M bits are set and the total size is around 140MB.
 tested-commands:
 - bitcount
 tested-groups:
@@ -28,10 +35,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: --command "BITCOUNT users __key__ -1" --key-maximum 1000000000 --key-minimum 1 --key-prefix "" --command-key-pattern R --distinct-client-seed --test-time 120
+  arguments: --command "BITCOUNT users __key__ -1" --key-maximum 1000000000 --key-minimum
+    1 --key-prefix "" --command-key-pattern R --distinct-client-seed --test-time 120
   resources:
     requests:
       cpus: '2'
       memory: 2g
 priority: 19

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-2-elements-geopos.yml CHANGED Viewed

@@ -1,6 +1,8 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-2-elements-geopos
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 2 elements and comes from the example of https://redis.io/docs/latest/commands/geopos, and we query it using GEOPOS command.'
+description: Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key
+  contains 2 elements and comes from the example of https://redis.io/docs/latest/commands/geopos,
+  and we query it using GEOPOS command.
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,7 +12,10 @@ dbconfig:
     requests:
       memory: 1g
   init_commands:
-   - '"GEOADD" "Sicily" "13.361389" "38.115556" "Palermo" "15.087269" "37.502669" "Catania"'
+  - '"GEOADD" "Sicily" "13.361389" "38.115556" "Palermo" "15.087269" "37.502669" "Catania"'
+  dataset_name: 1key-geo-2-elements
+  dataset_description: This dataset contains 1 GEO key with 2 elements, representing
+    locations in Sicily.
 tested-groups:
 - geo
 tested-commands:
@@ -23,10 +28,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: -c 50 -t 4 --command="GEOPOS Sicily Palermo Catania"  --hide-histogram --test-time 120
+  arguments: -c 50 -t 4 --command="GEOPOS Sicily Palermo Catania"  --hide-histogram
+    --test-time 120
   resources:
     requests:
       cpus: '4'
       memory: 2g
 priority: 138

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-2-elements-geosearch-fromlonlat-withcoord.yml CHANGED Viewed

@@ -1,6 +1,8 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-2-elements-geosearch-fromlonlat-withcoord
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 2 elements and comes from the example of https://redis.io/docs/latest/commands/geosearch, and we query it using GEOSEARCH command.'
+description: Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key
+  contains 2 elements and comes from the example of https://redis.io/docs/latest/commands/geosearch,
+  and we query it using GEOSEARCH command.
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,8 +12,11 @@ dbconfig:
     requests:
       memory: 1g
   init_commands:
-   - '"GEOADD" "Sicily" "13.361389" "38.115556" "Palermo" "15.087269" "37.502669" "Catania"'
-   - '"GEOADD" "Sicily" "12.758489" "38.788135" "edge1" "17.241510" "38.788135" "edge2"'
+  - '"GEOADD" "Sicily" "13.361389" "38.115556" "Palermo" "15.087269" "37.502669" "Catania"'
+  - '"GEOADD" "Sicily" "12.758489" "38.788135" "edge1" "17.241510" "38.788135" "edge2"'
+  dataset_name: 1key-geo-4-elements
+  dataset_description: This dataset contains 1 GEO key with 4 elements, representing
+    locations in Sicily.
 tested-groups:
 - geo
 tested-commands:
@@ -24,10 +29,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: -c 50 -t 4 --command="GEOSEARCH Sicily FROMLONLAT 15 37 BYBOX 400 400 km ASC WITHCOORD WITHDIST"  --hide-histogram --test-time 120
+  arguments: -c 50 -t 4 --command="GEOSEARCH Sicily FROMLONLAT 15 37 BYBOX 400 400
+    km ASC WITHCOORD WITHDIST"  --hide-histogram --test-time 120
   resources:
     requests:
       cpus: '4'
       memory: 2g
 priority: 138

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-60M-elements-geodist-pipeline-10.yml CHANGED Viewed

@@ -1,6 +1,8 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-60M-elements-geodist-pipeline-10
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 60841557 elements in it and we query it using GEODIST command between 2 elements. '
+description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO
+  key contains 60841557 elements in it and we query it using GEODIST command between
+  2 elements. '
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,6 +12,8 @@ dbconfig:
   resources:
     requests:
       memory: 6g
+  dataset_name: 1key-geo-60M-elements
+  dataset_description: This dataset contains 1 GEO key with 60 million elements.
 tested-groups:
 - geo
 tested-commands:
@@ -22,10 +26,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: --pipeline 10 -c 50 -t 4 --command="GEODIST key 1 2"  --hide-histogram --test-time 180
+  arguments: --pipeline 10 -c 50 -t 4 --command="GEODIST key 1 2"  --hide-histogram
+    --test-time 180
   resources:
     requests:
       cpus: '4'
       memory: 2g
 priority: 166

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-60M-elements-geodist.yml CHANGED Viewed

@@ -1,6 +1,8 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-60M-elements-geodist
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 60841557 elements in it and we query it using GEODIST command between 2 elements. '
+description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO
+  key contains 60841557 elements in it and we query it using GEODIST command between
+  2 elements. '
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,6 +12,8 @@ dbconfig:
   resources:
     requests:
       memory: 6g
+  dataset_name: 1key-geo-60M-elements
+  dataset_description: This dataset contains 1 GEO key with 60 million elements.
 tested-groups:
 - geo
 tested-commands:
@@ -22,10 +26,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: -c 50 -t 4 --command="GEODIST key 1 2"  --hide-histogram --test-time 180
+  arguments: -c 50 -t 4 --command="GEODIST key 1 2"  --hide-histogram --test-time
+    180
   resources:
     requests:
       cpus: '4'
       memory: 2g
 priority: 166

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-60M-elements-geohash-pipeline-10.yml CHANGED Viewed

@@ -1,6 +1,7 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-60M-elements-geohash-pipeline-10
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 60841557 elements in it and we query it using GEOHASH command. '
+description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO
+  key contains 60841557 elements in it and we query it using GEOHASH command. '
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,6 +11,8 @@ dbconfig:
   resources:
     requests:
       memory: 6g
+  dataset_name: 1key-geo-60M-elements
+  dataset_description: This dataset contains 1 GEO key with 60 million elements.
 tested-groups:
 - geo
 tested-commands:
@@ -22,10 +25,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: --pipeline 10 -c 50 -t 4 --command="GEOHASH key 1"  --hide-histogram --test-time 180
+  arguments: --pipeline 10 -c 50 -t 4 --command="GEOHASH key 1"  --hide-histogram
+    --test-time 180
   resources:
     requests:
       cpus: '4'
       memory: 2g
 priority: 170

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-60M-elements-geohash.yml CHANGED Viewed

@@ -1,6 +1,7 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-60M-elements-geohash
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 60841557 elements in it and we query it using GEOHASH command. '
+description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO
+  key contains 60841557 elements in it and we query it using GEOHASH command. '
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,6 +11,8 @@ dbconfig:
   resources:
     requests:
       memory: 6g
+  dataset_name: 1key-geo-60M-elements
+  dataset_description: This dataset contains 1 GEO key with 60 million elements.
 tested-groups:
 - geo
 tested-commands:
@@ -27,5 +30,4 @@ clientconfig:
     requests:
       cpus: '4'
       memory: 2g
 priority: 170

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-60M-elements-geopos-pipeline-10.yml CHANGED Viewed

@@ -1,6 +1,7 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-60M-elements-geopos-pipeline-10
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 60841557 elements in it and we query it using GEOPOS command. '
+description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO
+  key contains 60841557 elements in it and we query it using GEOPOS command. '
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,6 +11,8 @@ dbconfig:
   resources:
     requests:
       memory: 6g
+  dataset_name: 1key-geo-60M-elements
+  dataset_description: This dataset contains 1 GEO key with 60 million elements.
 tested-groups:
 - geo
 tested-commands:
@@ -22,10 +25,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: --pipeline 10 -c 50 -t 4 --command="GEOPOS key 1"  --hide-histogram --test-time 180
+  arguments: --pipeline 10 -c 50 -t 4 --command="GEOPOS key 1"  --hide-histogram --test-time
+    180
   resources:
     requests:
       cpus: '4'
       memory: 2g
 priority: 138

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-60M-elements-geopos.yml CHANGED Viewed

@@ -1,6 +1,7 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-60M-elements-geopos
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 60841557 elements in it and we query it using GEOPOS command. '
+description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO
+  key contains 60841557 elements in it and we query it using GEOPOS command. '
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,6 +11,8 @@ dbconfig:
   resources:
     requests:
       memory: 6g
+  dataset_name: 1key-geo-60M-elements
+  dataset_description: This dataset contains 1 GEO key with 60 million elements.
 tested-groups:
 - geo
 tested-commands:
@@ -27,5 +30,4 @@ clientconfig:
     requests:
       cpus: '4'
       memory: 2g
 priority: 138

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-60M-elements-geosearch-fromlonlat-bybox.yml CHANGED Viewed

@@ -1,6 +1,8 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-60M-elements-geosearch-fromlonlat-bybox
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 60841557 elements in it and we query it using GEOSEARCH command that replies with a very large (~11K ) number of elements. '
+description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO
+  key contains 60841557 elements in it and we query it using GEOSEARCH command that
+  replies with a very large (~11K ) number of elements. '
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,6 +12,8 @@ dbconfig:
   resources:
     requests:
       memory: 6g
+  dataset_name: 1key-geo-60M-elements
+  dataset_description: This dataset contains 1 GEO key with 60 million elements.
 tested-groups:
 - geo
 tested-commands:
@@ -22,10 +26,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: -c 2 -t 4 --command="GEOSEARCH key FROMLONLAT 7.0 55.0 BYBOX 200 200 KM"  --hide-histogram --test-time 180
+  arguments: -c 2 -t 4 --command="GEOSEARCH key FROMLONLAT 7.0 55.0 BYBOX 200 200
+    KM"  --hide-histogram --test-time 180
   resources:
     requests:
       cpus: '4'
       memory: 2g
 priority: 158

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-60M-elements-geosearch-fromlonlat-pipeline-10.yml CHANGED Viewed

@@ -1,6 +1,8 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-60M-elements-geosearch-fromlonlat-pipeline-10
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 60841557 elements in it and we query it using GEOSEARCH command that replies with a very large (~100K ) number of elements. '
+description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO
+  key contains 60841557 elements in it and we query it using GEOSEARCH command that
+  replies with a very large (~100K ) number of elements. '
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,6 +12,8 @@ dbconfig:
   resources:
     requests:
       memory: 6g
+  dataset_name: 1key-geo-60M-elements
+  dataset_description: This dataset contains 1 GEO key with 60 million elements.
 tested-groups:
 - geo
 tested-commands:
@@ -22,10 +26,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: --pipeline 10 -c 2 -t 4 --command="GEOSEARCH key FROMLONLAT 7.0 55.0 BYRADIUS 200 KM"  --hide-histogram --test-time 180
+  arguments: --pipeline 10 -c 2 -t 4 --command="GEOSEARCH key FROMLONLAT 7.0 55.0
+    BYRADIUS 200 KM"  --hide-histogram --test-time 180
   resources:
     requests:
       cpus: '4'
       memory: 2g
 priority: 158

redis_benchmarks_specification/test-suites/memtier_benchmark-1key-geo-60M-elements-geosearch-fromlonlat.yml CHANGED Viewed

@@ -1,6 +1,8 @@
 version: 0.4
 name: memtier_benchmark-1key-geo-60M-elements-geosearch-fromlonlat
-description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO key contains 60841557 elements in it and we query it using GEOSEARCH command that replies with a very large (~100K ) number of elements. '
+description: 'Runs memtier_benchmark, for a keyspace length of 1 GEO key. The GEO
+  key contains 60841557 elements in it and we query it using GEOSEARCH command that
+  replies with a very large (~100K ) number of elements. '
 dbconfig:
   configuration-parameters:
     save: '""'
@@ -10,6 +12,8 @@ dbconfig:
   resources:
     requests:
       memory: 6g
+  dataset_name: 1key-geo-60M-elements
+  dataset_description: This dataset contains 1 GEO key with 60 million elements.
 tested-groups:
 - geo
 tested-commands:
@@ -22,10 +26,10 @@ build-variants:
 clientconfig:
   run_image: redislabs/memtier_benchmark:edge
   tool: memtier_benchmark
-  arguments: -c 2 -t 4 --command="GEOSEARCH key FROMLONLAT 7.0 55.0 BYRADIUS 200 KM"  --hide-histogram --test-time 180
+  arguments: -c 2 -t 4 --command="GEOSEARCH key FROMLONLAT 7.0 55.0 BYRADIUS 200 KM"  --hide-histogram
+    --test-time 180
   resources:
     requests:
       cpus: '4'
       memory: 2g
 priority: 158

redis-benchmarks-specification 0.1.291__py3-none-any.whl → 0.1.292__py3-none-any.whl

Potentially problematic release.

redis-benchmarks-specification 0.1.291py3-none-any.whl → 0.1.292py3-none-any.whl