[Matthias247]

The most problematic thing about the state of the world for web framework benchmarks is that some of them drop a lot of real world requirements while showcasing high RPS.

E.g. a signficant number of frameworks on the techempower benchmark don't run with any timeouts in the various stages of a HTTP request lifecycle. That would mean if one would deploy those in the real world the server would sooner or later run out of memory or fd's due to broken client connections. Once you add timeouts, performance would already drop.

Then there is logging and metrics, which are absolutely required for any production setup, but never included in any of those proof of concept setups.

If the performance after those mandatory things is added drops 2 to 4x, the conclusions from the benchmarks can be very different.