Highly efficient client for Pixelflut
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
Jan Speckamp 91826ea600
update README
il y a 4 mois
benchmarks document ideas, add readme img il y a 4 mois
.gitignore add binary to gitignore il y a 4 mois
IDEAS.md document ideas, add readme img il y a 4 mois
LICENSE Initial commit il y a 4 mois
README.md update README il y a 4 mois
main.go restore performance from before refactor il y a 4 mois

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