speckij
/
Hochwasser
mirror of https://github.com/SpeckiJ/Hochwasser.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
51 Commits 7 Branches 0 Tags 3.1 MiB
Go 93.9%
Shell 6.1%
Go to file
Norwin Roosen fc85b32233
more gifs & stupid jokes 
watch our RoI explode as our unicorn startup disrupts the entire pixel sector!11
 		2020-12-31 14:35:54 +01:00
benchmarks more gifs & stupid jokes 2020-12-31 14:35:54 +01:00
pixelflut graceful connection errors 2020-12-31 10:23:13 +01:00
render fix pattern size regression 2020-12-29 21:09:00 +01:00
rpc refactor main 2020-12-31 09:57:02 +01:00
.gitignore add binary to gitignore 2019-01-11 18:30:27 +01:00
IDEAS.md idea: p2p job distribution 2020-01-14 15:26:16 +01:00
LICENSE Initial commit 2019-01-06 21:54:30 +01:00
README.md more gifs & stupid jokes 2020-12-31 14:35:54 +01:00
main.go rpc on random port, if using local shorthand 2020-12-31 12:51:37 +01:00

README.md

🌊🌊🌊 Hochwasser 🌊🤽🌊

Highly efficient, distributed Pixelflut client.

Hochwasser brings back the /fun/ in social DDoSing!

No more micro-ddosing: Get Hochwasser now and experience highs never seen before!111!

  • Can send static images, text, generated patterns (animations upcoming)
  • REPL enables fast iterations
  • CnC server + client architecture (it's webscale!) (can also run in a single process)
  • Faster than sturmflut (in some benchmarks at least)
  • No dependencies (pixelflut apparently was considered a primary use case in the design of golang's stdlib 👍)

build / install

  1. have a go installation >= 1.12
  2. go get github.com/SpeckiJ/Hochwasser
  3. go install github.com/SpeckiJ/Hochwasser

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 1234
go run main.go -image benchmark/test.png -connections 10

screenshot: 55 Gbps of hochwasser

55 Gbps on average! 🌊🌊🌊

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