Benchmarks: the memory the service took, measured again
Bjolang's peak in the service's closed loop was inflated by how its program gathered samples, and Go's matched run was given that peak as its limit. With the program fixed, Bjolang peaks at 369 MB on all cores, and Go, given the larger corrected .NET peak, at 364. 🤖 Generated with [ECA](https://eca.dev) Co-Authored-By: eca-agent <git@eca.dev>
This commit is contained in:
parent
ba5c7afc9d
commit
671ad9ac88
1 changed files with 2 additions and 2 deletions
|
|
@ -957,9 +957,9 @@ In a closed loop, 1000 clients send 1000 requests each, each one as soon as the
|
||||||
| Program | all cores: wall | CPU | p99.9 | memory | 4 cores: wall | CPU | p99.9 |
|
| Program | all cores: wall | CPU | p99.9 | memory | 4 cores: wall | CPU | p99.9 |
|
||||||
|------------------+-----------------+---------+--------+--------+---------------+---------+--------|
|
|------------------+-----------------+---------+--------+--------+---------------+---------+--------|
|
||||||
| Go | 397 ms | 5552 ms | 5.7 ms | 27 MB | 475 ms | 1832 ms | 3.4 ms |
|
| Go | 397 ms | 5552 ms | 5.7 ms | 27 MB | 475 ms | 1832 ms | 3.4 ms |
|
||||||
| Go, same memory | 258 | 4076 | 3.2 | 399 | 414 | 1641 | 3.5 |
|
| Go, same memory | 258 | 4076 | 3.2 | 364 | 414 | 1641 | 3.5 |
|
||||||
| Hopac | 411 | 8903 | 9.8 | 387 | 296 | 1161 | 4.2 |
|
| Hopac | 411 | 8903 | 9.8 | 387 | 296 | 1161 | 4.2 |
|
||||||
| Bjolang | 254 | 5211 | 5.5 | 423 | 407 | 1571 | 4.7 |
|
| Bjolang | 254 | 5211 | 5.5 | 369 | 407 | 1571 | 4.7 |
|
||||||
}
|
}
|
||||||
|
|
||||||
On all cores Bjolang and Go with the same memory finish together, and Go uses a fifth less CPU and has the shorter tail. On four cores Hopac is clearly the fastest, and Bjolang and Go are close.
|
On all cores Bjolang and Go with the same memory finish together, and Go uses a fifth less CPU and has the shorter tail. On four cores Hopac is clearly the fastest, and Bjolang and Go are close.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue