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
-
-
What sort of machines are you running that on?
-
Ancient ones. 2 hosts on the left have 2x Xeon E5420 (Harpertown) each (8c8t total per host), right side has 1x E5520 (Nehalem-EP) (4c8c total). We rewrote the entire application and optimized the critical path to make it work out. New hardware is in the pipeline.
- Show replies
New conversation -
-
-
os miniodio por ser tan jodidamente eficientes xD esto parece esparta a la hora de elegir sitios xD y el sistema no peta nuncaaa!!!!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
La verdad es que vuestro trabajo es admirable edición tras edición, al que igual que el resto de la org de la
@euskalencounter. Eso si nos quitais el aliciente a los participantes de que tiramos los servers de la Euskal como hace unos años. -
Los servers no sólo se caían por el F5 ;-)
End of conversation
New conversation -
-
-
What kind of cluster do you make? I'm kinda interested into this :)
-
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).
- Show replies
New conversation -
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.