Increase HTTP performance by fitting in the initial TCP slow start window
1–7 of 7 posts
Re: Increase HTTP performance by fitting in the initial TCP slow start window
#2edit: maybe i'm confusing the receive window with something else.
Re: Increase HTTP performance by fitting in the initial TCP slow start window
#3Its a nit-pick, but the article talks a lot about packets in flight, yet tcp doesn't actually care about amount of packets in flight, as much as the amount of bytes in flight, and conflating the two just irks me. edit: maybe i'm confusing the receive window with something else.
https://en.wikipedia.org/wiki/TCP_congestion_control#Congest...
Re: Increase HTTP performance by fitting in the initial TCP slow start window
#4Re: Increase HTTP performance by fitting in the initial TCP slow start window
#5[0] http://packet.city/ (Warning: loud audio)
Re: Increase HTTP performance by fitting in the initial TCP slow start window
#6If you want fast initial load, then there is packet.city [0], "the greatest website to ever fit in a single TCP packet." :-) It also has a few other optimizations to make the response as fast as possible that are discussed on its github. [1] [0] http://packet.city/ (Warning: loud audio) [1] https://github.com/diracdeltas/FastestWebsiteEver
echo 1 > /proc/sys/net/ipv4/tcp_low_latency
That was deprecated in 2017. The sysctl is still there, but doesn't actually do anything in newer kernels. There are a few other ways to lower latency at the expense of throughput but I will let folks research that themselves.