Slashdot Mirror


IEEE Seeks Consensus on Ethernet Transfer Speed Standard

New submitter h2okies writes "CNET's News.com reports that the IEEE will start today to form the new standards for Ethernet and data transfer. 'The standard, to be produced by the Institute of Electrical and Electronics Engineers, will likely reach data-transfer speeds between 400 gigabits per second and 1 terabit per second. For comparison, that latter speed would be enough to copy 20 full-length Blu-ray movies in a second.' The IEEE also reports on how the speed needs of the internet continue to double every year. Of what consequence will this new standard be if the last mile is still stuck on beep & creep?"

24 of 92 comments (clear)

  1. Hype! by fm6 · · Score: 4, Funny

    Ethernet transfers never use more than a fraction of available bandwidth. So it's 2 blu-ray discs per second, 4 tops!

    1. Re:Hype! by MyLongNickName · · Score: 2

      I have had the results of SQL queries nearly max out my Ethernet connection (96Mbps)

      I told you it wasn't good to use a CROSS JOIN across all of your Access tables.

      --
      See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
    2. Re:Hype! by DJRumpy · · Score: 2

      I'm talking about protocol overhead.

      For example, all things being equal, a computer connected to a hub via a stock ethernet cable with a guaranteed link speed up and down should produce a result that's generally in the same area each time (hence the 'real world').

      It's not a difficult concept. We're not asking for a rating for every conceivable configuration, but best case real world numbers. WiFi theoreticals are nowhere near their real world numbers.

    3. Re:Hype! by vlm · · Score: 2, Insightful

      Unfortunately I have met several programmers who do exactly that. Usually recent refugees from homemade .csv land.
      Then they go on an epic bender of why SQL is not webscale and we need to use nosql solutions etc etc.
      I realize this sounds like a daily WTF post but I've also seen people implement sorting in the app instead of letting the DB do it. Madness.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    4. Re:Hype! by jeffmeden · · Score: 4, Funny

      Unfortunately I have met several programmers who do exactly that. Usually recent refugees from homemade .csv land.
      Then they go on an epic bender of why SQL is not webscale and we need to use nosql solutions etc etc.
      I realize this sounds like a daily WTF post but I've also seen people implement sorting in the app instead of letting the DB do it. Madness.

      Why would I trust the lousy SQL server app to properly implement a superior bubble sort algorithm?

    5. Re:Hype! by keltor · · Score: 2, Informative

      AC is 100% correct provided we're dealing with a local Access database and not Access fronting a SQL Server - in the latter case, all of the queries and what not take place on the SQL Server and not on the client. The latter case is not uncommon with Internal Applications that started off as an Access application and were later converted to run on SQL Server.

    6. Re:Hype! by TheRaven64 · · Score: 2

      But running what? Are you measuring the speed of delivering ethernet frames? Or of IPv4 packets? Or IPv6 packets? Or of payload carried by TCP packets on either?

      --
      I am TheRaven on Soylent News
    7. Re:Hype! by dgatwood · · Score: 2

      Now, one thing that many businesses want would be the idea of clients with no local storage, or perhaps even remove all processing in the local "terminal", and have a central server provide EVERYTHING.

      The last thing most businesses want are dumb terminals. It doesn't matter how fast the link is. A thin-client business is a business that ceases to function if the very-expensive server goes down. The few businesses I've seen that want thin clients are mostly in retail, and their networking needs are usually met quite well by 10BASE-T.... Most businesses prefer the robustness and redundancy of computers that can mostly function independently.

      For the residential market, there will also be some who go with a central "server" for all their music and videos in the home, and for that, higher speed links would be welcomed.

      No, they wouldn't. Even for most of those folks, 100 megabits per second is more than fast enough. Most users who set up a central video server haven't even bothered to upgrade to gigabit yet, much less 10 gigabit, much less terabit. You can reliably stream HD video over Wi-Fi. You pretty much have to have insane networking needs to want to go past gigabit. Even Blu-Ray HD video has a maximum data rate of 40 Mbps. So to require more than gigabit speeds, you would have to be streaming 25+ Blu-Ray-quality high definition video streams. And your server would have to be able to serve 25+ Blu-Ray-quality high-def streams simultaneously.

      We've gotten to the point where in-home networking is way more than fast enough to suit even the most demanding home users, and all but the absolute most demanding business users. Improving LANs is not a useful thing to do right now. That time and energy should be expended where it will actually do some good in the real world, which means improving the speed of WANs, not LANs.

      Basically, think outside your perception of "the general public", and look at where things WILL be.

      I am. I still don't see the point. You have two options for servers: making the servers bigger or making the servers more numerous. Unless you are doing something where strict synchronization is important, there's no benefit to one versus the other, which means there's no real benefit for making LANs faster. Those rare exceptions are things like render farms, build farms, etc. and are such tiny exceptions to the rule that they almost aren't worth seriously pondering. So the number of people or companies that would be helped by terabit LANs even in a decade or two is going to be measured in the single-digit millions of computers, give or take. By contrast, the number of folks that would be helped by faster WANs even today would be measured in the single-digit billions of computers. On that scale, the benefit from faster LANs is a rounding error.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

  2. 20 bluray per tbit? by VMaN · · Score: 5, Insightful

    I think someone got their bits and bytes mixed up...

    1. Re:20 bluray per tbit? by JavaBear · · Score: 2

      That always happen.
      With a little overhead, 1 Tbit/s is at most 100GiB a second. 2 Blu rays.

    2. Re:20 bluray per tbit? by fustakrakich · · Score: 2

      It's much worse than that. Somebody's reading comprehension isn't quite up to par

      FTFA: "enough to copy two-and-a-half full-length Blu-ray movies in a second."

      --
      “He’s not deformed, he’s just drunk!”
    3. Re:20 bluray per tbit? by fustakrakich · · Score: 2

      Whooops!!

      Correction: "Updated 10:05 a.m. PT August 20 to correct the 1Tbps data-transfer speed in terms of Blu-ray disc copying times."

      --
      “He’s not deformed, he’s just drunk!”
    4. Re:20 bluray per tbit? by Frnknstn · · Score: 2

      1 Terabit a second on the wire translates to about 100 Gigabytes a second of actual data transfer. Most modern encoding schemes and encapsulation protocols average 10 bits to represent an octet.

      --
      If it's in you sig, it's in your post.
    5. Re:20 bluray per tbit? by ericloewe · · Score: 2

      Ethernet's specs account for encoding overhead. That means 1Gb/s is 1Gb/s minus protocol overhead, not 800Mb/s minus protocol overhead.

  3. Consequence for the last mile? None for ages. by jandrese · · Score: 3, Insightful

    How important is 400G to the last mile? You might as well ask how important a new high bypass turbine engine for jumbo jets will be to my motorcycle. It's for a totally different market. We're just barely getting to the point where it starts to make sense for early adopters to get 10G Ethernet on their ridiculously tricked out boxes (and industry has been using it for backhaul for some time now), and 1G Ethernet is still gross overkill for the majority of users. We have at least gotten to the point where 10MB Ethernet is too slow however.

    --

    I read the internet for the articles.
  4. not so much hype by Chirs · · Score: 2

    It's pretty easy to max out a 100Mbit ethernet link. Gigabit is also doable with a bit of work. It's a bit harder to max out a 10G port but it can be done with multiple queues and large packets. Once you hit 10G you really need to be using multiple queues spread across multiple CPUs and offloading as much as possible to hardware.

    1. Re:not so much hype by AaronW · · Score: 2

      I have no problem saturating 10G links, but then again I'm working on multi-core CPUs with 10-32 cores optimized for networking (the 10G interfaces are built-in to the CPU). I have a PCIe NIC card on my desk with 4 10Gbe ports on it (along with a 32-core CPU).

      It's also neat when you can say you're running Linux on your NIC card (it can even run Debian).

      --
      This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
  5. Re:Consequence for the last mile? None for ages. by Shatrat · · Score: 4, Insightful

    Consequences to me in long haul fiber optic transport? Massive.
    Depending on how they implement 400G and Terabit it may affect the transport systems I deploy today, given that those speeds will likely require gridless DWDM which is currently just on the roadmap for most vendors.
    Then, once it does come out, if our infrastructure is ready for it we will probably be able to deploy a Terabit link for the same price as 3 or 4 100G links. By that time 100G will start feeling a little tight anyway if we keep up the 50% a year growth rate.

    There are no consequences to the last mile, for the same reason 100G has no consequences in the last mile.
    Even 10G I only see used in the last mile to large customers like wireless backhaul or healthcare.
    It's a silly summary but still an important topic.

    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
  6. Re:Consequence for the last mile? None for ages. by zbobet2012 · · Score: 3, Interesting

    Agreed, the summary is really quite stupid. It does matter to the last mile since the last mile isn't currently the limiting factor in most downloads, but rather backhaul bandwidth is. Also it really matters for trans-continental lines, where upgrading the routers without having to upgrade the fiber can mean massive improvements without huge costs.

  7. We did this last time, and wasted a bunch of time. by Above · · Score: 4, Insightful

    Last time around there was a question about 40GE or 100GE. Largely (although not exactly) server guys pushed a 40GE standard for a number of reasons (cost, time to market, cabling issues, and bus-throughput of the machines), and the network guys pushed to stay with 100GE. Some 40GE (pre-standard?) made it out the door first, but it's basically not a big enough jump (just LAG 4x10GE cheaper) so there is no real point. 100GE is starting to gain traction as doing a 10x10GE LAG causes reliability and management issues.

    This diversion probably delayed 100GE getting to market by 12-24 months, and the vast majority of folks, even server folks, now think 40GE was a mistake.

    Why is the IEEE even asking this question again? The results are going to be basically the same, for basically the same reasons. 1Tbe should be the next jump, and they should get working on it pronto.

  8. Re:We did this last time, and wasted a bunch of ti by mvar · · Score: 2

    Why is the IEEE even asking this question again? The results are going to be basically the same, for basically the same reasons. 1Tbe should be the next jump, and they should get working on it pronto.

    Because the companies that make the hardware are going to sell more modules :-P
    I can't understand why the author is even mentioning laptops and PCs on this article. First make sure you can utilize the existing 1gbps technology, then see how to implement faster interfaces. Right now the bottleneck at home ethernet is slow hard drives and cheap "gigabit" NICs that underperform.

  9. Re:not worth it in most cases by KingMotley · · Score: 2

    Nah. My NAS (low end) maxes out my 1Gbps connection easily, and they claim I can team two 1Gbps connections together and it will fill them up. Based on the CPU usage and I/O, I'd say that it could do much more than that if it had better connectivity options. It's not unreasonable to need 10Gbps connections, although yes, to actually use all the bandwidth between any two connections would be more difficult. Most enterprise SANs and some NASs use RAM and SSDs as caching mechanisms and can easily saturate a 10Gbps link itself.

    10Gbps = 1250MBps. My OCZ Revo could saturate that, easily.

  10. Re:not worth it in most cases by SuricouRaven · · Score: 2

    The most common reason for giving a server that much network capacity is virtualisation. A server hosting a collection of VMs will have hardware that substantial, and all those VMs sharing one physical interface will put the 10G to good use.

  11. Re:We did this last time, and wasted a bunch of ti by Anonymous Coward · · Score: 2, Informative

    The confusion between 40G ethernet and 100G ethernet is vast. But the actual reason for the standard has nothing to do with time-to-market or technological limitations beyond 40G. The 40G ethernet standard is designed to run ethernet over telco OC768 links. This standard allows vendors to support OC768 with the same hardware they use in a 100Gbps ethernet port.