4 ms·
250 rps in absolute terms is not enormous; and peaks of 25 times relative to base load is not unheard of. What I think you are indicating is that you have a ve
by SideburnsOfDoom 10y ago
250 rps in absolute terms is not enormous; and peaks of 25 times relative to base load is not unheard of.
What I think you are indicating is that you have a very unusual thing that ELB is not set up to handle: you go from base to peak load in seconds flat. Or even less? That's interesting and quite unlike the very common model of human visitors to a website ramping up, that ELB is likely designed around.
- jamiesonbecker 10y agoI'm still addicted to AWS, but Google hit 1M rps with only a seven minute scale time according to their blog way back in 2013. https://cloudplatform.googleblog.com/2013/11/compute-engine-load-balancing-hits-1-million-requests-per-second.html https://cloudplatform.googleblog.com/2013/11/compute-engine-... My biggest issue with ELB is how long it takes for the initial instances to get added to a new ELB.. it takes f-o-r-v-e-r... I've seen it take as long as fifteen minutes, even with no load. I'm hoping ALB fixes that.
- vacri 10y agoRe: adding to ELB, I haven't had that experience - for me it's been pretty reliably in line with the healthcheck config (2 healthchecks x 30 sec apart = 60ish seconds to add). Or are you including instance spin-up time in that number?