News for hackers. Stuff that matters.
Re:Scaling HipChat Using ElasticSearch And Redis by taspeotis on Tuesday January 07, 2014 @03:34AM (#7016287)
If you take the frontend servers out of the equation it's still 52 servers for 60 messages per second.
Re:Scaling HipChat Using ElasticSearch And Redis by msmithstubbs on Tuesday January 07, 2014 @04:30AM (#7016404)
My guess: the 60 messages per second is an average. Monday morning in the US timezones might see several multiples of that. Weekends could be a lot lower.
Re:Scaling HipChat Using ElasticSearch And Redis by powdahound on Tuesday January 07, 2014 @08:51AM (#7017253)
It's definitely very bursty. On weekends and holidays things are much more quiet. During peak load we'll be in the hundreds/sec. Also keep in mind that chat messages don't actually make up the majority of the traffic we serve; it's presence information (away, idle, available), people connecting/disconnecting, etc. (I'm one of the HipChat co-founders.)
Re:Scaling HipChat Using ElasticSearch And Redis by hox on Tuesday January 07, 2014 @07:51PM (#7021042)
And? The article makes no mention of what each server is responsible for, how much redundancy is built in (this is AWS where nodes die on a whim), whether all of these servers are used for production or if there is a spread across dev and staging environments, etc.

When all of these factors are considered, 52 servers isn't a huge number.