I will be happy to contribute Reactor and Spring benchmarks, but the from a quick look, I don't think the current benchmark give a useful indication of the performance you will have in a real web application, ie. just benchmarking returning a String from GET endpoint is maybe useful to check you have no a basic performance issue, but I would not use that to compare Web Frameworks. Something implying request path parsing, content negotiation and JSON serialization of a data coming with some latency and more that a single route defined would give a much more interesting overview of web framework performances.