Skip to content
Highly efficient client for Pixelflut (https://cccgoe.de/wiki/Pixelflut)
Branch: master
Clone or download
SpeckiJ update README
updated readme to relativieren statement without proof
Latest commit 91826ea Jan 23, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
benchmarks document ideas, add readme img Jan 22, 2019
.gitignore add binary to gitignore Jan 11, 2019
IDEAS.md document ideas, add readme img Jan 22, 2019
LICENSE Initial commit Jan 6, 2019
README.md update README Jan 23, 2019
main.go restore performance from before refactor Jan 22, 2019

README.md

🌊🌊🌊 Hochwasser 🌊🤽🌊

Highly efficient client for Pixelflut: Faster than sturmflut! (In some benchmarks at least)

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 doesn't seem to be CPU limited, as turbo-boost doesn't kick in.

To reproduce, run the following commands in separate shells:

iperf -s -p 1337
go run main.go -image benchmark/test.png -connection 10

screenshot: 55 Gbps of hochwasser

55 Gbps on average! 🌊🌊🌊

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 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.

future ideas

For future ideas check IDEAS

You can’t perform that action at this time.