Highly efficient client for Pixelflut
Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.
Norwin 3f0acd9694 refactor pixelflut package into proper API 2 tygodni temu
benchmarks document ideas, add readme img 1 rok temu
pixelflut refactor pixelflut package into proper API 2 tygodni temu
.gitignore add binary to gitignore 1 rok temu
IDEAS.md idea: p2p job distribution 1 miesiąc temu
LICENSE Initial commit 1 rok temu
README.md update README 1 rok temu
io.go refactor code into separate files 3 tygodni temu
main.go refactor pixelflut package into proper API 2 tygodni temu

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