News for hackers. Stuff that matters.
Re:Google Fiber Was Doomed from the Start by ovi256 on Wednesday March 15, 2017 @03:50PM (#13879184)
The 15 Mbps is TCP bandwidth, and the 100 Mbps is physical layer bitrate. They are not comparable. There are overheads and latency and packet loss can reduce how much physical bitrate TCP can use. So the 4k stream may or may not do great in 100mpbs.

Also, how about a second 4k screen ? Multiple TVs are the norm in American homes. How about multiple tablets or mobile devices consuming HD streams ?

It seems current access link infrastructure in the US cannot support current TV viewing habits, if all the TVs were switched to 4k digital streams.

Re:Google Fiber Was Doomed from the Start by rayiner on Wednesday March 15, 2017 @06:28PM (#13880468)
> The 15 Mbps is TCP bandwidth, and the 100 Mbps is physical layer bitrate. They are not comparable.

In practice TCP gets very close to the link rate unless you have latency much higher than what you typically have on cable/fiber. Fast.com (which "performs a series of downloads from Netflix servers" according to Netflix) benchmarks at 155 mbps on my 150/150 connection. (Cable/fiber systems are usually provisioned at a higher link rate than what is marketed: http://www.dslreports.com/faq/15643).

Re:Google Fiber Was Doomed from the Start by brians on Wednesday March 15, 2017 @07:15PM (#13880829)
I'm pretty sure fast.com, like Netflix, uses either UDP and its own congestion control or multiple TCP streams, depending on client details.
Re:Google Fiber Was Doomed from the Start by rayiner on Wednesday March 15, 2017 @07:19PM (#13880848)
I can get over 150 on single TCP stream tests like dslreports as well.