9 ms·
Wouldn't you be doing something horribly wrong if you couldn't serve 70k requests a day? It's actually less than 1 a second: 70000 / (60 * 60 * 24) = .81 I thi
by tbrock 13y ago
Wouldn't you be doing something horribly wrong if you couldn't serve 70k requests a day? It's actually less than 1 a second: 70000 / (60 * 60 * 24) = .81
I think this article is more about distributed systems being costly (yes) and perhaps overly complicated for the types of applications most people build. I agree. However, you could easily do the same with Linux.
- icedchai 13y agoyou can serve 70k/requests day on a 386 from 1989.
- jzwinck 13y agoRequests to a typical smallish site will not be uniformly distributed--not by a long shot. Given that the peak is what matters, if we might get a day's worth of traffic in a single hour, that's 19 requests per second instead of 0.8. Those 19 transactions per second will still sound tiny to many people, but a couple months ago we heard that Mt. Gox could only do 37 TPS. So 70k requests per day is not nothing, especially assuming non-uniform distribution, minimal effort to optimize performance, and cheap hardware (or virtual hardware).
- venomsnake 13y agoOn my home dev machine which is nothing to brag about (i5-750 overclocked to 4.2 ) golang was able to process that per second on a single core if you keep the static stuff prezipped in the ram.