How to Troubleshoot Throughput and TCP Windows 

First 30 seconds are golden.

The application sent 64k to TCP with the no_delay option. The Receive Window was 1M, you see that in the TCP Seq graph. Many apps will pause after the first 64k and wait for an ack (it's like an artificial TCP window), but this program is using a technique called double buffering to prevent the pause.. But still one of the best videos I've seen on this.

This is my first contact with packet analysis and it seems like a world of magic, suddenly weird things make sense. This looks just too useful

I was able to increase my grpc streaming throughput by over 3x (110Mbps > 400+Mbps) by watching this simple video

These are great videos! Thank you sir!

19:00 I've stumbled across this "not the network" opinion, often from ISP's, but if the packet size settings etc are wrong then that's a network technical issue, networks should be configured to work with standard OS settings, especially if the ISP also is in charge of the LAN. I understand that you mean that it's not the physical network, but how can you prove that with results like that, unless you setup everything with the right settings and prove that it works with the right settings. P.S. Awesome video, and funniest intro to any IT video yet!

i'm wondering why we don't see these errors (tcp window full) on client-side captures?

the best one

♪ ...the space between... ♪

You completely left out the transverse octet byte reference in your calculations. This makes your data irrelevant.

0:47 In that order. Thank you, and not likely because I'm too far away. Oh, and it's illegal. ;-) 6:16 No it's not. 128 K would be 131072 bytes. 19:00 If this is how you address people... :-(