The first 5 minutes of @euskalencounter #EE26 reservations, at 5x speed. Our servers survived with zero failed requests. Another year, another huge success for #noF5day.pic.twitter.com/wLkun03f5H
-
Show this thread
-
The peak at 10:00 CEST is everyone hitting the "Reserve" button all at once. There's a slight lull as people go through the payment gateway, before moving on to seat selection. Seat selection is DB-heavy, hence the extended load on tohru (DB master). 5024 total seats available.pic.twitter.com/LQg1IzHto8
4 replies 3 retweets 24 likesShow this thread -
Replying to @marcan42
What kind of cluster do you make? I'm kinda interested into this :)
1 reply 0 retweets 0 likes -
Replying to @MSyaifuddin_
It's just one server doing everything (DB+webapp+nginx frontend), and two older servers just running extra instances of the webapp to balance things a bit, plus aux services. All three servers are old hardware, but we optimized the app quite a bit (see other replies).
1 reply 0 retweets 2 likes -
Replying to @marcan42
Ah I see. I tought you are using db replication as well. It looks great though.
1 reply 0 retweets 0 likes
We'll set up real DB replication with the new hardware. Right now we take hourly DB backups onto one of the other hosts (already saved my ass once with those).
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.