Found this in the depths of my storage. Not sure where its from but might improve the day of some people ^^
this post was submitted on 02 Oct 2024
713 points (99.3% liked)
Programmer Humor
19813 readers
167 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
To be fair, because of window size management it only takes 1% packet loss to cause a catastrophic drop in speed.
Packet loss in TCP is only ever handled as a signal of extreme network congestion. It was never intended to go over a lossy link like wifi.
Doesn't wifi have its own retrial protocol? It's been a long time since I've read the standard, but I think it's almost lossless from the POV of TCP.
I believe so, yes. Every 802.11 frame is effectively ACK'd. Makes a mockery of OSI layering, but so does everything else.
None built in from what I recall. That was from back in 2011, so it's possible things changed since.
Reading through, it looks like retries do exist, but remember that duplicate packets are treated as a window reset, so it's possible that transmission succeeded but the ack was lost.
I remember the project demos from the course though - one team implemented some form of fast retry on two laptops and had one guy walk out and away. With regular wifi he didn't even make it to the end of the hall before the video dropped out. With their custom stack he made it out of the building before it went.
I'll need to dig through to find the name of what they did.
On the other side of the spectrum packet loss is a key feature of some of the layers below tcp, like path-mtu discovery.