Skip to content

Conversation

@paulorsousa
Copy link
Collaborator

  • memtier_benchmark-1Mkeys-string-setget200c-4KiB-pipeline-1.yml
  • memtier_benchmark-1Mkeys-string-setget200c-4KiB-pipeline-10.yml

Both test suites:

  • Use 1M key keyspace with 10% SETs and 90% GETs (1:10 ratio)
  • Test 4096-byte string data size
  • Include io-threads topology variants (2, 4, 8 threads) and standalone
  • Run for 180 seconds with 4 threads, each using 50 clients

These benchmarks complement existing pipeline testing by providing 4KiB data size coverage, helping assess Redis performance with larger payloads.

…ne variations

- memtier_benchmark-1Mkeys-string-setget200c-4KiB-pipeline-1.yml
- memtier_benchmark-1Mkeys-string-setget200c-4KiB-pipeline-10.yml

Both test suites:
- Use 1M key keyspace with 10% SETs and 90% GETs (1:10 ratio)
- Test 4096-byte string data size
- Include io-threads topology variants (2, 4, 8 threads) and standalone
- Run for 180 seconds with 4 threads, each using 50 clients

These benchmarks complement existing pipeline testing by providing 4KiB
data size coverage, helping assess Redis performance with larger payloads.
Copy link
Collaborator

@fcostaoliveira fcostaoliveira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. thank you @paulorsousa

@fcostaoliveira fcostaoliveira merged commit e1c2da1 into main Nov 17, 2025
9 checks passed
@fcostaoliveira fcostaoliveira deleted the feature/add-4kib-string-setget-pipeline-benchmarks branch November 17, 2025 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants