Surviving the Grand National
summary
Explains how a betting platform runs repeated load-test cycles, finds an NFS-backed PHP bottleneck, a long-term memory leak and a Redis cluster nearing memory limits, then fixes Redis live via Redis hot-reconfigure and autoscaling to avoid customer logouts. Describes reliance on a single Infomix monolith for settlement, the batch/throttle strategy during the “danger zone,” and hitting a record 10,000+ bets per minute—surpassing a rival while keeping customers working.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:24Grand National
- 1:36What a betting website traffic looks like
- 5:35How Sky Betting Gaming is organised
- 6:46Technology Product Marketing
- 11:20Load Testing
- 14:14Unexpected Things
- 14:36Failures
- 17:51Making the day work
- 18:43Team organisation
- 20:16Customer experience
- 20:31Risk management
- 20:58Allwell
- 23:14Redshift
- 23:35Session Management
- 25:06Danger Zone
- 25:27Managing Database Load
- 26:58Summary
related talks
15mGrand National 2021: Managing Extreme Online Demand at William Hill
47mFrom Legacy to High-Load: Evolution of a Web Application
39mUnder the Hood: Engineering at William Hill
42mPlanning To Fail
36mMake It Fast
10mSurviving the 2008 Elections
50mBuilding and Operating Online Shops under Extreme Load
10mRedis, databaza në memorie me shumë përdorime