Highly efficient client for Pixelflut
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Norwin 3f0acd9694 refactor pixelflut package into proper API 5 months ago
benchmarks document ideas, add readme img 1 year ago
pixelflut refactor pixelflut package into proper API 5 months ago
.gitignore add binary to gitignore 1 year ago
IDEAS.md idea: p2p job distribution 5 months ago
LICENSE Initial commit 1 year ago
README.md update README 1 year ago
io.go refactor code into separate files 5 months ago
main.go refactor pixelflut package into proper API 5 months ago


🌊🌊🌊 Hochwasser 🌊🤽🌊

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

Can currently only send a single picture though.


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

55 Gbps on average! 🌊🌊🌊

sturmflut (./sturmflut 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