Hacker News new | past | comments | ask | show | jobs | submit login

I just don't understand how this can be this slow. What on earth is it doing to get 193 requests per second on static, cached content?

The article doesn't dig too deep into this sadly, rather just accepts that it's slow and uses a different tool.

But seriously, this is responding to a request with the content of a file. How can it be 100,000x slower than the naive solution. What can it possibly be doing, and why is it maxxing out the CPU?

If no-one else looks into this, I might get around to it.




I'm getting 2586 RPS with the default next.js starter app on a low budget laptop. Something isn't right here.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: