31 ms·
> 1.5 million requests a second, and holds trillions of “objects” My god. I used to think I was a bit of a rock star, with (rails) web sites exceeding 100 requ
by venus 13y ago
> 1.5 million requests a second, and holds trillions of “objects”
My god. I used to think I was a bit of a rock star, with (rails) web sites exceeding 100 requests/second on my resume. 1.5 million requests per second ... I cannot even really imagine that.
- codex 13y agoThese get requests are likely sharded among a large number of machines. Viewed that way, it's much more manageable. Want to service more requests? Just add more machines. 1.5M relational queries on the other hand--that would be impressive.
- StavrosK 13y agoOver 15,000 machines, it's roughly the same thing!
- lukeschlather 13y agoIt all depends on how many servers you have, as well as what sort of databases/database complexity. For a laughably trivial site, a single host could do a lot of requests per second without too much effort. For a normal Rails app running on a handful of hosts, 100 requests per second is nothing to scoff at, especially if you're on your own.
- ddeck 13y agoThese are spread over an enormous number of machines. OT, but for truly impressive single machine performance, check out the LMAX FX trading platform, which can handle 6 million orders per second on a single core on commodity hardware.....in Java. [1] [1] http://martinfowler.com/articles/lmax.html http://martinfowler.com/articles/lmax.html