Slashdot Mirror
Terabit Ethernet Is Dead, For Now
Nerval's Lobster writes "Sorry, everybody: terabit Ethernet looks like it will have to wait a while longer. The IEEE 802.3 Industry Connections Higher Speed Ethernet Consensus group met this week in Geneva, Switzerland, with attendees concluding—almost to a man—that 400 Gbits/s should be the next step in the evolution of Ethernet. A straw poll at its conclusion found that 61 of the 62 attendees that voted supported 400 Gbits/s as the basis for the near term 'call for interest,' or CFI. The bandwidth call to arms was sounded by a July report by the IEEE, which concluded that, if current trends continue, networks will need to support capacity requirements of 1 terabit per second in 2015 and 10 terabits per second by 2020. In 2015 there will be nearly 15 billion fixed and mobile-networked devices and machine-to-machine connections."
No, unbounded latency. It'll happen, just not yet.
We need terabit Ethernet NOW, not in a decade.
You know my 5 year old nephew keeps confusing need and want too.
How much are you prepared to pay for this desire? If it will cost say 4 times greater per bit to implement Terabit with current technology do you still want it?
"The weirdest thing about a mind, is that every answer that you find, is the basis of a brand new cliche" -
I realised I wasn't being clear about why they can't define the standard now and wait for the technology to catch up.
A standard like this is always a trade off based on the currently available technology, How fast are your analogue transistors, how much processing power do you have to do forward error correction. How fast are your ADCs/DACs to do signal shaping? This determines things like which coding schemes can you use. Also what market needs this and what costs are acceptable, for example DWDM and all the associated costs is perfectly acceptable if fibre is comparatively expensive, however even though in the 90s that would have been the only way to do 10G now we have the capability to do it electrically; designing the spec too soon and guessing is a really bad idea. We don't know how 20nm and lower process nodes are going to behave well enough to predict what their characteristics will be when this technology reaches maturity, to get that wrong is to end up with a standard that either under performs or is over expensive.
Put it another way, the processor architecture you would choose to achieve 80MFLOPS in 1976 is very different from the architecture you would choose in 2006. Telecomms has exactly the same concerns.
"The weirdest thing about a mind, is that every answer that you find, is the basis of a brand new cliche" -
And what exactly is he doing over ethernet that needs that much speed? I'm only just now looking at upgrading our small business network to gigabit. A couple of years ago the cost of a 48 port gigabit switch was pretty high, but now it's very reasonable
which is totally what she said
You may discover that you can't have what you want. There are real physical limitations we have to deal with. One issue, with regards to copper Ethernet, that we are having is keeping something that remains compatible with older style wiring. Sticking with 8P8C and UTP is becoming a real issue for higher speeds. At some point we may have to have a break where new standards require a different kind of jack and connector.
Also in terms of "data center only" devices that isn't how things work. You care what data centers use because you connect to them. There can be big advantages in terms of cost, simplicity, and latency, to stick all on one spec. So 40gbps or 400gbps could well be useful. No, maybe you don't see that to your desktop, but that doesn't mean it doesn't get used in the switching infrastructure in your company.
Also each order of magnitude you go up with Ethernet makes the next matter less. It's going to be awhile before there's any real need for 10gbps to the desktop. 1gbps is just plenty fast enough for most things. You can use things over a 1gbps link like they were on your local system and not see much of a performance penalty (latency is a bigger issue than speed in most things at that point). I mean consider that the original SATA spec is only 1.5gbps.
As for 100gbps, it'll take some major increases in what we do before there is a need for that to the desktop, if ever. 10gbps is just an amazing amount of bandwidth to a single computer. It is enough to do multiple uncompressed 1080p60 video streams, almost enough to do a 4k uncompressed video stream.
Big bandwidth is more of a data center/ISP need than a desktop need. 1gbps to the desktop is fine and will continue to be fine for quite some time. However to deliver that, you are going to need more than 1gbps above your connection.
As a parent of a young one I also hear this 500×/day. But what's the cost of "Terabit now and you're safe for a decade" versus "400Gb now, then rewire & replace all your gear in 3-5 years for 750Gb (if there isn't a standards war you have to gamble on), and then do that all over again in another 3-5 years for 1.1Gb"? Because that's the kind of creep we've seen since the early days of token ring and then 10BaseT. Manufacturers certainly want the step-by-step option but the admins and engineers? Not so much so.
Hardly any 10 base T systems bother with the CDMA/CD system that original ethernet had , in fact its more like a serial protocol rather than a broadcast "in the ether" one now. WHy not just give it a new name?