Is There a Place for a $500 Ethernet Card?
prostoalex writes "ComputerWorld magazine runs a story on Level 5 Networks, which emerged from the stealth startup status with its own brand of network cards and software called EtherFabric. The company claims they are reducing the load on the servers CPUs and improve the communications between the servers. And it's not vaporware: 'The EtherFabric software shipping Monday runs on the Linux kernel 2.4 and 2.6, with support for Windows and Unix coming in the first half of next year. High volume pricing is $295 for a two-port, 1GB-per-port EtherFabric network interface card and software, while low volume quantities start from $495.'"
I wonder what has changed? I have never known the CPU to get dragged down by network traffic, but maybe in the network server markets it is different, However with the Ethernet chipsets being designed into the motherboard and integrated into the tight circle of RAM and CPU, it isn't clear there is a need for this.
How long before the network control is put into the CPU? It is going to be tough to beat that type of performance.
A most overlooked advantage to owning a computer is if they foul up there's no law against wacking them around a bit.
Is There a Place for a $500 Ethernet Card?
Of course there is, assuming the card performs as advertised. Sheer conjecture: the card likely has a lot of the smarts onboard. Maybe it has some of the TCP and IP stuff on board too (checksum, etc). Compare that to a crapbox $10.95 RealTek[a] card which generates interrupts like mad because it has no smarts and you'd probably be very suprised. (Think of comparing a decent hardware modem to a software based WinModem.)
[a] I had a sales-drone at Computer Boulevard here in Winnipeg just RAVE about RealTek cards. I said I really wanted 3 Intel or 3COM cards for a new work proxy server and he said 'Why? RealTeks are way cheaper and run at the same speed!' Retard.
Trolling is a art,
if your internet connection is anything less than fiber, which is about 99.9% of all connections? Not to mention the fact that not many computers can actually handle that much data at once anyway.
This isn't exactly an entirely new concept. Intel have been selling their ethernet chips with built in SSL accelerators for quite some time, and the advantage of offloading duties from the software to the hardware (see Intel etherexpress vs RealTek style cards) is obvious. Whether these cards offload enough of the normal duties of a typical cluster node to be worthwhile should be interesting to see, as there are a wide variety of cluster load types and obviously these cards will have a niche to fit into alongside their competitors in the diverse set of demands around cluster networks. As for the price tag, I seem to remember gigabit cards being extremely expensive a few years back, and its probably pretty competitive with where they're aiming this product, alongside myrinet and infiniband.
Business Voyeur
I give Realtek 6 months tops to make thier own knock-off of the card for $24.95.
You say things that offend me and I can deal with it. Can you?
The Pentagon.
But not necessarily where the vendors think it is.
Back when I was working at a startup developing anti-DDoS technology, one of the biggest problems we were faced when implemented GigE, was the load on the PCI bus. (This was before we started using PCI-X).
It depends on exactly how customisable the network card software is, but if you could plonk a couple of those into whatever system you wanted - and if the cards themselves could do, say, signature detection of various flood types, or basic analysis of traffic trends then that is a very definite market.
I realise the core issue is not addressed (if your physical pipe is full, then you're fucked), but it takes the load of dropping the malicious packets off the host CPU so it can attempt to service whatever valid traffic actually gets through.
And then there is IP fragmentation. Bad fragments? Perhaps a dodgy fragmentation implementation in the stack? (you know which OS I mean) Lets just drop that before the host sees it and crashes.
I don't know, I can't find any real information describing what they do, but I can certainly see uses for this.
The name Level 5 refers to the network protocol stack where level 5 delivers data from the network to the application, according to Karr. The company isn't concerned about any potential confusion with Internet Protocol telecom Level 3 Communications Inc. On the contrary, he quipped, "It's working in our favor. People say, 'Yes, we've heard of you. You're a big company.'"
As lawyers at Level 3 begin salivating at thought of all of the potential lawsuits.
We use Filers for storage at Gigabit speeds. Compared to our SAN/FC evironments, we see much higher CPU utilisation on our Sol 8 boxes, especially when attempting to get to Gigibit speeds.
$500 for a network card you have to have a good reason that you will need it. I am sure there are applications that will utilize it but for the price it may not be worth it. With sub $500 computers coming to age. It is probably cheaper just to split all your services onto smaller boxen and have a load balancing switch/router. Computers are cheap today $500 for a network card is steep and will only fill a niche market. Perhaps if the price was in the $50 range it would be more widely accepted. But with good enough systems at 1k and additional 500 could be used for a faster CPU other then a faster network CPU
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
I highly doubt they're aiming these cards at the general public. The kind of folks who worry about this kind of performance aren't buying $500 computers, they're buying $5,000 + computers, and trying to tweak every ounce of performance out of them. I'm willing to bet my employer is going to look pretty seriously at these cards for some of our heavy-use systems.
Sometimes you can't "split all your services onto smaller boxen and have a load balancing switch/router". Not everything on the network is a web server.
If this card can do most of the work of IPSEC for me, it'd be a big win.
My main concern though is that with two ports, how can I be absolutely certain the packet has to go through my firewall rules before it can go anywhere?
Of course, the extra ports could be an advantage. If it could handle all the rules for you, then it might even be capable of functioning as a layer 4 switch and sending out a new IP packet before completely recieving said packet.
But, I'd want all the software on that card to be Open Source.
Need a Python, C++, Unix, Linux develop
Virtualization.
These are the kinds of NICs that would be put into a datacenter that is leaning heavily toward VMware GSX or ESX servers. Any bit of offload of the CPU in sharing the NICs is a good thing.
What?
"Smaller boxes" is relative. Google's cluster nodes are dual Xeons with terabyte+ HDs. For Google it is small, for anyone else, that is powerful computer you're going to be paying alot for. If you're buying one of those computers you're probably going to look at one of these cards, and that is exactly the market they're looking for.
I looked at their benchmark web page http://www.level5networks.com/prod_etherfabricperf .htm where they claim that a typical PC with "conventional" ethernet burns 83.5% of CPU for communication overhead while only 16.5% remain to the application.
But they don't say which CPU was used - probably an 850 MHz Pentium III or something similar outdated.
Fact is, on a current 3.x GHz Pentium IV or an equivalent Athlon or Opteron the communication overhead is in one digit range, percentage-wise.
A famous computer science quote is:
"Lies, damned lies and benchmarks"
and another one is
"Don't trust any statistics that you haven't forged yourself."
Dedicated Linux servers (root access) $45 p.M.
As CPUs get faster an interrupt costs you more in terms of lost CPU time. So, reducing the number of interrupts is more important now than ever before.
My 100 Mbs ethernet card generates about 5k interrupts / second when transferring data at about 30 Mbps. Gigabit cards are engineered to hold interrupts until a few packets of data come in so that a DMA can move a larger chunks of data. If this NIC reduces the use of interrupts even further (say by off boarding computation or even the entire TCP/IP stack and thus allows for even larger DMA transfers) the impact could be substantial.
Unfortunetly, my knowledge of computer innards stops here, so I can't calculate how much cpu time 5000 interrupts actually take or how the new PCI-Express bus changes interrupt processing or how much a benefit it would be to have say only 1000 interrupts / second instead of the 5000.
Interrupts are the one place where it's not remotely true. A faster processor will allow your system to handle significantly more interrupts. The whole interrupt model needs to be thrown out and replaced with something much better.
And while I'm at it, there are many cases where it's not true. Wherever you have a significant bottleneck, hardware acceleration helps tremendously. Tasks like encryption and (HighDef) video playback can max-out the highest-end systems available, while a $50 card can handle those tasks easily.
I don't think purpose-built hardware everywhere is the answer, but I do think having an FPIC/ASIC as a standard computer component could make for incredible speed improvements in most/all of the tasks that are hard for CPUs to perform.
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
It's just like people who see gold ends on something and figure it's the automatic winner in any contest.
:P
Never mind that using gold connectors and non-gold connectors together causes corrosion.
It's been a long time.
- Erecting yet another edifice brings on the huge and unavoidable overheads of yet another different CPU instruction set, yet another real-time scheduler, another code base, another set of performance and timing bottlenecks. Another group of programmers. Another set of in-circuit emulators, debugging tools, and system kernel. Another cycle of testing, bug fixes, updates.
- It sets up a split in the programming team-- there's now much more reason for finger-pointing and argument and mistrust.
- The extra money would usually buy you another CPU and lots of RAM, resources that would benefit every part of the system, not just the network I/O.
- The separate I/O processor usually requires the geekiest and least communicative of the programmers-- not a good thing. The manuals for the I/O card are likely to be very brief and sketchy, and rarely up to date.
- The I/O processor is almost always at least one generation of silicon technology older than the CPU, so even though the glossy brochures just drip with Speeeed! and Vrooom!-y adjectives, it's not that speedy in comparison to the CPU.
For examples, see the $4000 graphics co-processor that IBM tried to sell for the PC (IIRC the CPU could outdo-it). The various disk-compression cards for the PC. Also see the serial ports on the Mac IIvx (very expensive and not noticeably better). Don't forget the P-code chip for the PDP-11/03. All very expensive and blase' performance/$.