3 ms·
What I miss from that benchmark: - CPU/memory consumption - higher concurrency level (4096 for i7 at least) - dependency graphs - latency/concurrency etc.
by snaky 13y ago
What I miss from that benchmark:
- CPU/memory consumption
- higher concurrency level (4096 for i7 at least)
- dependency graphs - latency/concurrency etc.
- krg 13y agoAgreed, this would be interesting. It's under discussion: https://github.com/TechEmpower/FrameworkBenchmarks/issues/108 https://github.com/TechEmpower/FrameworkBenchmarks/issues/10...
- snaky 13y agoNice! I hope we will see it in next rounds. There is a big difference between "it serves 1200 rps" and "it serves 1200 rps and barely seen in top" actually
- bhauer 13y agoYes, but to set expectations before we even implement the server statistics capture we have planned: we want the CPU to be fully utilized for most of these tests. If you barely see the server showing up in top, something is probably going wrong (or you've run into a different limit such as disk or network). We're testing the maximum number of requests a server can handle per second, so the optimum is for the CPU to be fully utilized. A different test would measure how much CPU is used if I want to serve X requests per second.