Am 20.04.2017 um 21:33 schrieb Tomáš Chaloupka:
On Thu, 20 Apr 2017 16:24:59 GMT, Tomáš Chaloupka wrote:
https://www.techempower.com/benchmarks/previews/round14
It finally seems to at least pass all the tests. Also it uses the new vibe-core beta.
But I would expect much higher position at least in the plaintext test.
I've tried the plaintext test on my Broadwell NTB with i5-5300U
new vibe-core
[tomas@E7450 wrk]$ ./wrk -c 10 -d 30 -t 4 http://localhost:8080/plaintext Running 30s test @ http://localhost:8080/plaintext 4 threads and 10 connections Thread Stats Avg Stdev Max +/- Stdev Latency 0.86ms 2.16ms 83.77ms 99.19% Req/Sec 2.64k 291.25 3.40k 82.08% 315459 requests in 30.02s, 50.24MB read Requests/sec: 10507.38 Transfer/sec: 1.67MBold
[tomas@E7450 wrk]$ ./wrk -c 10 -d 30 -t 4 http://localhost:8080/plaintext Running 30s test @ http://localhost:8080/plaintext 4 threads and 10 connections Thread Stats Avg Stdev Max +/- Stdev Latency 430.97us 0.86ms 20.36ms 96.28% Req/Sec 6.04k 1.24k 9.09k 68.58% 721024 requests in 30.03s, 111.39MB read Requests/sec: 24012.03 Transfer/sec: 3.71MBCompiled with dmd 2.074.0 with dub -b release
Compared to for example go-std:
[tomas@E7450 wrk]$ ./wrk -c 10 -d 30 -t 4 http://localhost:8080/plaintext Running 30s test @ http://localhost:8080/plaintext 4 threads and 10 connections Thread Stats Avg Stdev Max +/- Stdev Latency 728.27us 2.72ms 107.30ms 96.02% Req/Sec 6.62k 1.14k 10.02k 74.67% 790419 requests in 30.04s, 95.73MB read Requests/sec: 26315.10 Transfer/sec: 3.19MBCompiled with go1.7.5
It almost looks like it never scales beyond a single core for some
reason. I'll have to start another profiling round to be sure, but it
could be related to the switch to std.experimental.allocator. Maybe
the GC is now suddenly the bottleneck.
BTW, thanks a lot for fixing the benchmark suite! This is something that
I always had in mind as an important issue, but could never find the
time for. I'll try look into the performance issue within the next few days.