name: "search-asm-ftsb-1M-enwiki_abstract-hashes-fulltext-search-sortby-limit-0-100-sparse-hashslots"
description: "
             - name: enwiki-abstract [details here](https://github.com/RediSearch/ftsb/blob/master/docs/enwiki-abstract-benchmark/description.md),
                     from English-language Wikipedia:Database page abstracts.
                     This use case generates 3 TEXT fields per document, and focusses on full text queries performance.
                     Specifically for this testcase:
                      - Type (read/write/mixed): read
                      - Query type: Simple 1 Word Query
                      - Query sample: Abraham
             - total docs: 5.9 million
             - fields per doc: 3 TEXT sortable fields
             - average doc size: 227 bytes

            This use case aims to test how much the _SLOTS_INFO serialization/deserialization affects performance when the hash slot info is of max length (ranges of one slot (odd and even hash slots in different shards))
             "

metadata:
  component: "search"
setups:
  - oss-cluster-02-primaries
  - oss-cluster-04-primaries

dbconfig:
  - dataset_name: "ftsb-1M-enwiki_abstract-hashes"
  - init_commands:
    - '"FT.CREATE" "enwiki_abstract" "ON" "HASH" "SCHEMA" "title" "text" "SORTABLE" "url" "text" "SORTABLE" "abstract" "text" "SORTABLE"'
  - asm_cluster_state:
    - 'SPARSE'
  - tool: ftsb_redisearch
  - parameters:
    - workers: 64
    - reporting-period: 1s
    - input: "https://s3.amazonaws.com/benchmarks.redislabs/redisearch/datasets/1M-enwiki_abstract-hashes/1M-enwiki_abstract-hashes.redisearch.commands.SETUP.csv"
clientconfig:
  benchmark_type: "read-only"
  tool: memtier_benchmark
  arguments: "--test-time 120 -c 32 -t 1 --hide-histogram --command 'FT.SEARCH enwiki_abstract * SORTBY abstract ASC LIMIT 0 100'"
