You have too much network bandwidth!!

One last thing worht mentioning.  How much a stream is delayed at the start is not an indicator of how big a buffer the client may keep.  For instance, Netflix may try to keep a 10 second buffer, but delay playing by only 2 seconds or less.  It may backfill after starting, or you may have high enough bandwidth that the first 10 seconds of data (say 50 MB) comes in a second... so it starts playback as soon as it can. 

Kind of neat how buffering and TCP packet management hide all of this from the consumer until things go really wrong.  This process is happening all the time around us and we don't even know it.

@richardbrand - 1000 times per second is literally 0.000001% of the bandwidth. Besides, streaming does not require ACK confirmation, protocols can work without it.

Correct! I use a 160mb/s network for 35 bucks a month. I stream movies flawlessly, I stream music flawlessly listening to flac, CD quality sound.

 It sounds just like the CD.  So the special network gear and high speed is not needed.

@erik_squires How about family members streaming video programming or any security camers in the house. With all the various ways to consume internet banddwidth, there's no such thing as too much bandwidth.

 How about family members streaming video programming or any security camers in the house. With all the various ways to consume internet banddwidth, there's no such thing as too much bandwidth.

1.  Don't take my post too literally.

2. Worth thinking about when readers wonder if they can improve their Qobuz/Tidal stream with 10 GigE switches. :)