11–20 of 107 posts
Earlier quoted context omitted.
netflix last year was reported at 37% in NA, so I suspect it will continue to be a contender as it gets more traction globally. http://appleinsider.com/articles/16/01/20/netflix-boasts-37-... 'peak download internet traffic' whatever that means.
Traffic during peak hours. Peak demand is what really matters for infrastructure.
"one out of four bytes that are delivered to end users across the Internet originate from Google" Such a mind blowing statement. Wonder when (if) they'll hit one-in-three bytes.
"one out of four bytes that are delivered to end users across the Internet originate from Google" Such a mind blowing statement. Wonder when (if) they'll hit one-in-three bytes.
I guess if Netflix ever switched from AWS to Google Cloud Platform...
"one out of four bytes that are delivered to end users across the Internet originate from Google" Such a mind blowing statement. Wonder when (if) they'll hit one-in-three bytes.
> Wonder when (if) they'll hit one-in-three bytes. I guess if Netflix ever switched from AWS to Google Cloud Platform...
I don't know, feels like a massive waste of resources and if Google is doing it simply because it can. It's probably much cheaper for everyone else to handle latency/throughput problems on the client side and application level, sticking to all the traditional networking, but not relying on it for quality. Even in the web browser we already can send all kinds of asynchronous requests to multiple servers in multiple da…
This has pushed the decision back from the routers to the servers, where it scales with the number of hosts handling connections and can additionally be determined per /session/ instead of per packet. That state is held where sessions already need to be stored anyway instead of being duplicated in a router where it's entirely a burden.
Can someone ELI5 the difference between this and https://azure.microsoft.com/en-us/services/expressroute/ ? Is the technology principle the same?
Espresso is a system for controlling BGP peering using application-fed metrics. It's basically complicated source routing.
It will never be sufficient. A good backbone infrastructure doesn't compensate for the fact that the majority of users don't have ISP choices especially for fast speed fixed/mobile networks.
Earlier quoted context omitted.
> Wonder when (if) they'll hit one-in-three bytes. I guess if Netflix ever switched from AWS to Google Cloud Platform...
99% of Netflix bytes are largely served from Netflix's own CDN + a cadre of third party CDNs. The bytes to/from AWS isn't trivial by itself but relatively negligible compared to video traffic.
I don't know, feels like a massive waste of resources and if Google is doing it simply because it can. It's probably much cheaper for everyone else to handle latency/throughput problems on the client side and application level, sticking to all the traditional networking, but not relying on it for quality. Even in the web browser we already can send all kinds of asynchronous requests to multiple servers in multiple da…