3 ms·
That's no longer necessary thanks to HTTP/2 Your webserver still has to spin off a thread for each request if you want to do substantial CPU work for each requ
by NavinF 6y ago
That's no longer necessary thanks to HTTP/2
Your webserver still has to spin off a thread for each request if you want to do substantial CPU work for each request, but rest assured you'll get all the requests at once from the browser. Not 6 at a time like in the dark ages
The RFC recommends at least 100 streams. See SETTINGS_MAX_CONCURRENT_STREAMS https://tools.ietf.org/html/rfc7540#section-6.5.2 https://tools.ietf.org/html/rfc7540#section-6.5.2