3 ms·
You raise a question, but there's a missing detail in your input - how many machines (and what kind) you are using. If you have 80,000,000 machines serving 80,
by beagle3 13y ago
You raise a question, but there's a missing detail in your input - how many machines (and what kind) you are using.
If you have 80,000,000 machines serving 80,000,000 requests - that's not very impressive. Even if you have 80 servers, that's extremely unimpressive.
If you can do all of that on 1 server, then YOU probably don't need async. In fact, unless you're wasting time, 80,000,000 averages less than 10 requests/second, and peak is likely less than 100 requests/second. That's really not much - I do that with interpreted python.
But every language does need facility for async processing.
edit: it's 1000/second, not 10/second, as everyone down here corrected. Apparently, I cannot math before coffee. (I don't drink coffee). Apologies.
fun mnemonic: the number of seconds in a day is 864e2. (eight-six-four-(e)-two).
- einhverfr 13y ago> In fact, unless you're wasting time, 80,000,000 averages less than 10 requests/second... Please show your math. I took 80000000 / (24 * 60 * 60) and I got 925. So you seem off by about two orders of magnitude.
- harrytuttle 13y agoYour math is off. It's on a bell curve. We're regionally tied so we have 80,000,000 requests, 90% of which are over a 5 hour period so we can hit 5000 requests a second on a fun day :) We do this on 10 servers. 4 front end, 4 back end, 2 database nodes. They are all hefty machines (FE=8xXeon,16Gb;BE=16xXeon,32Gb,DB=48xXeon,96Gb;Storage=12TiB SAN). Our peak cluster load is about 20% (the sweet spot). We don't need async, even if we lost half of our nodes.