speckij
/
Hochwasser
mirror of https://github.com/SpeckiJ/Hochwasser.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

fix benchmark readme

This commit is contained in:
Norwin Roosen 2019-01-10 23:10:44 +01:00
parent 3c31981fbb
commit 80756ae8c2
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -10,7 +10,8 @@ Can currently only send a single picture though.
## benchmark
The following benchmark was run on a max-spec X280 against version [d4c574b].
I could not figure out what the performance bottleneck is, but it is not CPU limited.
I could not figure out what the performance bottleneck is, but it doesn't seem
to be CPU limited, as turbo-boost doesn't kick in.
To reproduce, run the following commands in separate shells:
@ -25,9 +26,12 @@ go run main.go -image benchmark/test.png -connection 10
[sturmflut] (`./sturmflut 127.0.0.1:1337 benchmark/test.png -t 10`, version `8ec6ee9`) managed to get 48 Gpbs throughput on this system.
> Hint: Benchmarking throughput against the [pixelnuke][pixelflut_gh] is pointless,
as performance is then CPU-limited to ~1 Gbps by the server.
> Hint: Benchmarking throughput against the [pixelnuke][pixelflut_gh] server is
pointless, as performance is then CPU-limited to ~1 Gbps by the server.
Using [iperf] removes the server limitation.
This also means that these metrics of several Gbps are far higher than
realworld scenarios.
[d4c574b]: https://github.com/SpeckiJ/Hochwasser/commit/d4c574be103a7bad69349f29402694f51058184c
[pixelflut_gh]: https://github.com/defnull/pixelflut
[iperf]: https://iperf.fr/