Add comprehensive SET:GET mixed workload tests for essential data sizes #300
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add 32B SET:GET tests (default memtier size for community usage) - Add 100B SET:GET tests with expiration support for common use cases - Add 512B SET:GET tests (referenced in cloud provider documentation) - Add 1KB SET:GET tests (common benchmark size) - Include both pipeline 1 and pipeline 10 configurations - All tests use 50:50 SET:GET ratio for realistic mixed workloads - Tests cover 1M keyspace with proper preloading This completes the essential SET:GET benchmark coverage for the four most important data sizes used in Redis performance testing and documentation.
Add missing 'set' command to tested-commands list for 100B expiration tests. The stats tool detected that these tests use setex, get, and set commands but only had setex and get listed in the tested-commands section.
- Test 1: SET EX 3 (50M keys) - Short TTL expiration performance - Test 2: SET EX 20 (150M keys) - Medium TTL expiration performance - Test 3: SET EX 10 with precondition (50M+50M keys) - Mixed TTL scenarios - Test 4: SET→SET→DEL EX 120 (50M keys) - Command throughput without expiration - Test 5: SET→SET→DEL EX 36000 (10M keys) - Long TTL command throughput - Test 6: SET EX random range 20sec-30days (50M keys) - Wide TTL distribution - Test 7: SET EX 10 years (50M keys) - Very long TTL performance - Test 8: Multi-client AWS test (20M+80M keys) - Multi-client expiration All tests use realistic pipeline 10 configuration and cover various expiration scenarios for ebuckets performance testing.
- Changed all 8 expiration tests from single client (-c 1 -t 1) to standard configuration (-c 50 -t 4) - Updated CPU allocation from 2 to 4 cores to match thread count - Maintains pipeline 10 configuration for realistic testing - AWS multi-client test keeps its specific 4 clients/2 threads configuration as intended - All tests now follow consistent connection/thread patterns with existing test suite
paulorsousa
approved these changes
Jun 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This completes the essential SET:GET benchmark coverage for the four most important data sizes used in Redis performance testing and documentation.