IMPORTANT NOTE: Timing of sessions and room locations are subject to change.
The Sched app allows you to build your schedule but is not a substitute for your event registration. You must be registered for ValkeyConf to participate in the sessions. If you have not registered but would like to join us, please go to the event registration page to purchase a registration.
This schedule is automatically displayed in Central European Summer Time (UTC+02:00). To see the schedule in your preferred timezone, please select from the drop-down located at the bottom of the menu to the right.
Sign up or log in to add sessions to your schedule and sync them to your phone or calendar.
We run 840+ Redis 7.2.12 instances on AWS EKS serving ~1.64M operations per second. Facing a performance ceiling, fragmented client tooling, and a licensing dead-end after Redis left BSD, we migrated the entire fleet to Valkey 8.1.5 — with zero application code changes and sub-five-minute rollback. This talk is an evidence-first walkthrough. We'll cover what actually changed under the hood (production-ready I/O threading, Swiss Table memory layout, deterministic cluster failover) versus what stayed identical (wire protocol, data format, client libraries) — the distinction that made a fleet-wide engine swap a defensibly low-risk decision. We'll share the benchmark methodology behind our results — +31% throughput, −33% P99 latency, and 22–41% memory savings, confirmed across three independent tools — plus the blue-green rollout plan for both Sentinel and Cluster deployments.
