4 ms·
It looks like the bottleneck here is the database driver (or possibly ORM when used). The plaintext test shows a very different picture: https://www.techempowe
by dorfsmay 8y ago
It looks like the bottleneck here is the database driver (or possibly ORM when used). The plaintext test shows a very different picture:
https://www.techempower.com/benchmarks/#section=#section=data-r16&hw=ph&test=plaintext https://www.techempower.com/benchmarks/#section=#section=dat...
PS: As a side note, I do not like golang, my focus has been on python and now rust, but I am very impressed by both the plaintext and the DB test!
- tomchristie 8y agoI think TechEmpower are doing a great job on these generally, but the plaintext benchmark is problematic because they allow pipelining. (Which isn’t enabled in browsers, isn’t typically used in request libraries and tools, and has generally been sidelined) Frameworks which are tailored with that in place can get a big boost in the ratings there. If you want a measure of plain request/response I’d use the JSON benchmarks as the baseline.
- bpicolo 8y agoThe bottleneck on plaintext appears to potentially be physical network bandwidth. https://github.com/TechEmpower/FrameworkBenchmarks/issues/3538 https://github.com/TechEmpower/FrameworkBenchmarks/issues/35...
- dorfsmay 8y agoAgreed, but it shows the framework that are able to reduce their overhead, since they aren't all at 100% of the fastest.