Feat: speedometer (ratelimit for i/o)

[yunginnanet]

• Speedometer is an io.Writer wrapper that can limit the rate at which data is written to the underlying target.
• It can be given a capacity, which will cause it to return an error if the capacity is exceeded.
• It can also be given a speed limit, causing slow downs of data written to the underlying writer if the speed limit is exceeded.
• It is safe for concurrent use, but writers will block when slowed down.

(From: #11 (comment))

[github-actions]

GPT summary of 99403c3:

• Changed test name from "SynSynAckAck" to "limited TCP bandwidth" speedometer_test.go
• Added rate calculation to log output speedometer_test.go

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (4413fdb) 100.00% compared to head (c1ed133) 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##              main       #11    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files            3         4     +1     
  Lines          137       249   +112     
==========================================
+ Hits           137       249   +112     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ginger51011]

All in all I think this is great! I am not sure of the sync logic, it's hard enough in a language you know well to wrap your head around.

I hope my comments are somewhat useful, and not completely uncalled for.

[yunginnanet]

All in all I think this is great! I am not sure of the sync logic, it's hard enough in a language you know well to wrap your head around.

I hope my comments are somewhat useful, and not completely uncalled for.

definitely helpful! helped me spot some unused code in there that would have even costed us a few atomic CPU operations that effectively did nothing but waste our time. I appreciate it!

as for the synchronization, we can only hope that my unit tests (100% coverage at least) are robust enough to make sure i'm not a total dumbass :^)