3 ms·
I'm disappointed that 'prefork' version of fasthttp failed to run due to unknown (yet) reason. TechEmpower should publish benchmark logs later, so the problem w
by valyala 11y ago
I'm disappointed that 'prefork' version of fasthttp failed to run due to unknown (yet) reason. TechEmpower should publish benchmark logs later, so the problem with fasthttp in 'prefork' mode could be fixed in the Round 13.
Fasthttp starts distinct server process per CPU core in this mode. This should result in perfect scalability on multi-CPU machines.
- clishem 11y agoSee https://www.techempower.com/blog/2016/02/25/framework-benchmarks-round-12/ https://www.techempower.com/blog/2016/02/25/framework-benchm... , they needed to get this benchmark in quick, because they need to shift hardware soon. Maintainers weren't able to submit their patches to fix things. If you ask me it would have been better not to run this benchmark.
- deleted 11y ago[deleted]