Valkey 9.0 ElastiCache t3.small Client Latency
The Valkey 9.0 ElastiCache cache.t3.small benchmark on cache.t3.small now has a real load-generator-side latency signal. The earlier latency view was an empty placeholder, this run's ECS artifact includes Embedded Metric Format samples for ElastiCache/LoadGenerator / ClientLatency with p50, p99, and p99.9.
Valkey 9.0 ElastiCache t3.small benchmark
ElastiCache t4g.micro Results: Redis 7.1 and Valkey 7.2, 8.2, 9.0
The cache.t4g.micro result set currently splits into two useful signals: Valkey 7.2 leads throughput and client-side average latency, while Valkey 9.0 shows the lowest throughput variation and peak engine CPU. Redis 7.1 stays in the set as the Redis reference run.
Valkey 9.0 ElastiCache t4g.micro benchmark
Valkey 8.2 ElastiCache t4g.micro benchmark
Valkey 7.2 ElastiCache t4g.micro benchmark
Redis 7.1 ElastiCache t4g.micro benchmark
Hit Rate Fixed, Evictions Missing
After "When the Cache Never Warms Up", I went back and tuned the test itself. I wanted memtier to show some real cache hit rate during the run.
When the Cache Never Warms Up
I did not want the results to live only in CloudWatch. That works for running the test, but not so well for sharing or keeping the output around.
So I added the "Reporting" branch, and the first result is shown below.
Hardening the ElastiCache Benchmark: Observable Lifecycle & Durable S3 Exports
AWS ElastiCache Lab (built on Amazon ElastiCache) is a repeatable performance harness for comparing cache configurations under controlled load. Each run is time-boxed, produces exportable artifacts, and tears down deterministically to keep both cost and comparability under control.
As the harness scales up (more Amazon ECS tasks, higher memory fill rate), the bottleneck often moves away from ElastiCache itself and toward the lifecycle boundary: shutdown, exports, and verification. The engine can change (Redis today, Valkey next), the boundary and evidence pipeline should not.
