|Norwin 3f0acd9694 refactor pixelflut package into proper API||2 tygodni temu|
|benchmarks||1 rok temu|
|pixelflut||2 tygodni temu|
|.gitignore||1 rok temu|
|IDEAS.md||1 miesiąc temu|
|LICENSE||1 rok temu|
|README.md||1 rok temu|
|io.go||3 tygodni temu|
|main.go||2 tygodni temu|
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 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.
For future ideas check IDEAS