Ostro said:
| walsufnir said:
ehh... nintendo knew how big the update was. nintendo knew how much wiiu's they delivered. multiply, done. also they could've contacted the cdn-provider before as they have proficient knowledge on network-load for sure.
i don't want to blame nintendo alone, perhaps they just chose the wrong cdn. to me, this is not a big issue as i expected something like this. if it had been perfect at start i would have been surprised.
|
It's not about "Nintendo knew ...", it's about what they are able to test. Even if they did a test with approx. 1,000,000 simulated connections, it doesn't ensure that it will work this way in the real world with varying connection speeds, data and connection loss, a wide-spread network around the globe instead of in-house tests, etc. You can't test software like a car and then start using/selling it when it comes out of the gate.
|
it seems you don't know or understand how delivering much data over the internet works. there is no big server nintendo has that has to deliver the bandwidth and deal with the connection. please read http://en.wikipedia.org/wiki/Content_delivery_network this is, what nintendo has most probably done: made a contract with a cdn-provider. i don't blame only nintendo but also the cdn-provider which surely has much knowledge when it comes to high demand (bandwidth and/or connections).
edit: this was easy... google for "nintendo cdn", you will find http://pastebin.com/aB2GV3Bd.
then nslookup nus.cdn.shop.wii.com -> 80.239.148.163 which resolves to a339.d.akamai.net. akamai is one of the biggest if not *the* biggest cdn-provider. they *had* to know which demand is coming.
