No description
Arsalan Naeem
dc485647a0
Deploy Redis 7.0.12 (standalone) via Opstree community redis-operator (Helm-installed; OLM bundle unpack timed out post-cluster-reboot). Expose via NodePort and a TLS-passthrough Route (stunnel sidecar). Benchmarks: 2,000,000 ops SET+GET, 50 clients. Baseline: - Internal Service: SET 33,049 rps / 0.89 ms, GET 32,707 rps / 0.90 ms - External NodePort: SET 28,922 rps / 1.24 ms, GET 30,143 rps / 1.19 ms - External Route: SET 8,716 rps / 5.01 ms, GET 8,705 rps / 4.99 ms Route is latency-bound (HAProxy router + stunnel + Service hop ~5 ms RTT per command). Adding stunnel replicas / client threads / more clients gave only 7-15% gain. Pipelining is the lever: -P 16 takes Route to 157 K rps (18x), -P 32 -c 100 to 250-270 K rps. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| results | ||
| tls | ||
| .gitignore | ||
| expose-nodeport.yaml | ||
| internal-bench-pipelined.yaml | ||
| internal-bench.yaml | ||
| operator-sub.yaml | ||
| redis-cr.yaml | ||
| RESULTS.md | ||
| stunnel.yaml | ||