4 ms·

Exactly. Very few companies will need to reach 1000 reqs/s consistently, let alone 100k reqs/s. StackOverflow peaks at about 6000 reqs/s and it's an extremely

by pier25 4y ago

Exactly. Very few companies will need to reach 1000 reqs/s consistently, let alone 100k reqs/s. StackOverflow peaks at about 6000 reqs/s and it's an extremely popular website.

swyx 4y ago
got a source for this stackoverflow peak? also wondering what peak RPS is for HN. i feel like most (non consumer) startups would be like "ok if its good enough for HN its good enough for me"
- ksec 4y ago
  >got a source for this stackoverflow peak? It is [1] ( and should be ) pretty well known. 1.3 BILLION page view per month, 6K RPS with 9 ( Fairly Weak ) Servers, Sub 20ms response time with zero caching. >also wondering what peak RPS is for HN. Less than 100 RPS for logged in users. The number were pre 2020 but I doubt the current number is significantly higher. [1] https://stackexchange.com/performance https://stackexchange.com/performance
  - coder543 4y ago
    > Sub 20ms response time with zero caching. I mean... to be clear, they do tons of caching[0], which is certainly critical for their ability to have a non-cached response time of 20ms. Most of their responses should be coming from a cache, given the type of site they run, otherwise they would need a lot more servers. [0]: https://nickcraver.com/blog/2019/08/06/stack-overflow-how-we-do-app-caching/ https://nickcraver.com/blog/2019/08/06/stack-overflow-how-we...
- pier25 4y ago
  Their director of engineering did a podcast a couple of months ago: https://hanselminutes.com/847/engineering-stack-overflow-with-roberta-arcoverde https://hanselminutes.com/847/engineering-stack-overflow-wit...
redleggedfrog 4y ago
...that runs on .NET. :^P
datalopers 4y ago
Except low concurrency is often found alongside slow response time.
- tbalsam 4y ago
  Overly complex and feature-filled (or extremely barebones and "fast") frameworks can also have the property of giving no responses for additional months at a time. (i.e., sometimes "it works" is good enough, and our ego in design elegance doesn't need to get in the way of our need to keep existing as a business. If we need to rebuild or refactor later when we really know what we want, we can. :) )

by pier25 4y ago

Exactly. Very few companies will need to reach 1000 reqs/s consistently, let alone 100k reqs/s. StackOverflow peaks at about 6000 reqs/s and it's an extremely popular website.

swyx 4y ago

got a source for this stackoverflow peak? also wondering what peak RPS is for HN. i feel like most (non consumer) startups would be like "ok if its good enough for HN its good enough for me"

ksec 4y ago
>got a source for this stackoverflow peak? It is [1] ( and should be ) pretty well known. 1.3 BILLION page view per month, 6K RPS with 9 ( Fairly Weak ) Servers, Sub 20ms response time with zero caching. >also wondering what peak RPS is for HN. Less than 100 RPS for logged in users. The number were pre 2020 but I doubt the current number is significantly higher. [1] https://stackexchange.com/performance https://stackexchange.com/performance
- coder543 4y ago
  > Sub 20ms response time with zero caching. I mean... to be clear, they do tons of caching[0], which is certainly critical for their ability to have a non-cached response time of 20ms. Most of their responses should be coming from a cache, given the type of site they run, otherwise they would need a lot more servers. [0]: https://nickcraver.com/blog/2019/08/06/stack-overflow-how-we-do-app-caching/ https://nickcraver.com/blog/2019/08/06/stack-overflow-how-we...
pier25 4y ago
Their director of engineering did a podcast a couple of months ago: https://hanselminutes.com/847/engineering-stack-overflow-with-roberta-arcoverde https://hanselminutes.com/847/engineering-stack-overflow-wit...

redleggedfrog 4y ago

...that runs on .NET. :^P

datalopers 4y ago

Except low concurrency is often found alongside slow response time.

tbalsam 4y ago
Overly complex and feature-filled (or extremely barebones and "fast") frameworks can also have the property of giving no responses for additional months at a time. (i.e., sometimes "it works" is good enough, and our ego in design elegance doesn't need to get in the way of our need to keep existing as a business. If we need to rebuild or refactor later when we really know what we want, we can. :) )