Highly efficient client for Pixelflut
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
Jan Speckamp 91826ea600
update README
vor 5 Monaten
benchmarks document ideas, add readme img vor 5 Monaten
.gitignore add binary to gitignore vor 6 Monaten
IDEAS.md document ideas, add readme img vor 5 Monaten
LICENSE Initial commit vor 6 Monaten
README.md update README vor 5 Monaten
main.go restore performance from before refactor vor 5 Monaten

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

55 Gbps on average! 🌊🌊🌊

sturmflut 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