This is great! Having widely-deployed HTTP servers compete on performance is a nice win for the rest of us :)

I wonder whether they're also queueing for reads from the TCP connection? At least per their public comms, Facebook uses an interesting combination of CoDel and adaptive LIFO processing [0]: under load, they preferentially serve queued requests in last-in, first-out order to prioritize users who are likely still waiting for the response (vs those who gave up b/c the service is slow). It'd be amazing to have a widely-available webserver expose similar control knobs.

Anyhow, kudos to the .NET team!

[0]: https://queue.acm.org/detail.cfm?id=2839461

It’s interesting how impactful switching from a rudimentary lock to a thread-safe queue was.