 tiger72SexaT duorPPremium join:2001-03-28 Saint Louis, MO kudos:1 | 43 hops over existing infrastructure what makes this one interesting is that it required 43 hops, 3 times crossing the atlantic, and 450ms to get there over EXISTING Sprint infrastructure on a single 2.8ghz xeon with 1GB RAM.
that, at least to me is amazing. |
|
 justinAustralian join:1999-05-28 New York, NY kudos:7 | yeah thats a wall of data, but the ping time sucks  |
|
 | reply to tiger72 I am glad they are showing what today's off the shelf technology can do. This means that:
1) both their client and servers can handle incoming and outgoing high speed data delivery. 2) Sprint (and other high end ISP) are able to redeploy their existing fiber and routers to backbone locations that need it. 3) we are getting closer to HDTV two-way communication in the near future (2010) in our household.
The biggest bottleneck is getting new equipment to households at reasonable cost (digging up the ground). I am sorry but the existing telephone wire for DSL or hub-spoke cable infrastructure is not going to cut it. Also, I (and maybe others) will not be willing to pay the more money to Universal Service Fund (USF) to supply fiber to everyone household. I have the option of getting cable or DSL at a reasonable price rural users do not.
The end equipment is not the major cost since prices come down each year for better equipment. For example, what is stopping anyone from deploying a 5/8 port gigaswitch in their existing household to play multi-player high end games? The data transfer is not the problem but the end equipment processing the incoming/outgoing data. I backup my temp directory (7 gigabytes) to another hard disk via docking station and it takes about 10 minutes (Windows XP on laptop). It is not going to be any faster using gigaswitch to another machine.
I am glad these organizations are using existing equipment and infrastructure to test what can be done today. This will allow developers and equipment vendors (Intel, Cisco, UNIX, Microsoft, etc) to know what issues that will encounter. For example, what happens if you drop a packet? How do you recover the data at these speeds without slowing down the tranfer greatly? |
|