3 ms·
Yes. Bit errors are uncommon and range from benign to crash. Your storage has them, memory has them, network has them. Non error correcting memory very signi
by ddingus 10y ago
Yes.
Bit errors are uncommon and range from benign to crash.
Your storage has them, memory has them, network has them.
Non error correcting memory very significantly increases risk.
And this is the kind of risk you don't notice, until you do and when you do, it's often subtle, insidious, impossible to track down.
Servers absolutely. It's debatable on desktop, but we have huge RAM now. Might as well error correct. The bit error risk is small. Bigger RAM only adds to that possibility.
- VT_Drew 10y agoI wouldn't bother on a desktop or laptop. Servers absolutely.
- hashhar 10y agoI won't bother on a desktop. I've been using 4 machines for the last 17 years with storage varying from 10GB to 2TB and RAM varying from 128MB to 16GB and haven't personally seen any kind of data corruption in motion (or at rest for that matter). Only had 2 mechanical drives fail (though predictably). ECC is costly. The memory modules itself and the board required to support it properly.
- planteen 10y agoHave you not had a computer do something unexpected in the last 17 years? A bit flip might look like a kernel or application crash. Have you ever saved a file that couldn't later be opened by an application? You probably blamed the application for being buggy, but it could have been an upset. Bit flips / upsets cause all sorts of odd behavior.
- falcolas 10y ago> haven't personally seen any kind of data corruption in motion Ever had a program crash, hang, or act oddly? That's how data corruption in memory surfaces. Of course, non-perfect programs (i.e. all of them) act the same way, which means that differentiating memory corruption from misbehaving programs is hard. Fixing the memory errors will result in more stable system, but it still won't be perfect.
- justin66 10y ago> haven't personally seen any kind of data corruption How would you know? Unless your computer use has been literally trouble-free (and all your archived data has been verified for correctness somehow), you can't know that none of your glitches over the past 17 years has been due to memory errors.
- xenadu02 10y agoThe only reason ECC is costly is because Intel has a monopoly on the desktop/server chip market and they refuse to deploy ECC to consumer chips. The hardware is there, it's just fused disabled. If ECC were only the cost premium and we assumed a linear relationship then it should cost about 1/8 more than non-ECC DRAM. Unfortunately Intel's decisions have knock-on effects that ripple through the rest of the market. IIRC I saw somewhere that JDEC expects a future standard will require ECC to get acceptable error rates for all memory. At that point Intel won't have any choice.
- dom0 10y agoThis is a bit like an inverse magic stone argument ("This stone repels tigers — How do I know it works? — I'm not seeing any tigers around here, do you?").
- user5994461 10y agoI have been seeing numerous memory corruption on many of my computers, including end of life memory sticks and motherboards that died before my eyes. At work, including my sysadmin years, up to a very long time ago on stupid summer jobs fixing computers, I have spent countless man*months to debug issues that were ultimately caused by memory errors. All of that could have been avoided by using ECC.
- gyrgtyn 10y agoDoes it make any difference if you're using your desktop to compile stuff?
- ddingus 10y agoIf you want to be sure it's right, yes. Here is the thing: Without ECC, or even simple parity on the RAM, the CPU cannot validate a data transfer. In the 90s, a place I worked for had a server running non parity, non ECC RAM. That machine was fast and cheap. But it would demonstrate the most bizarre problems, from time to time. A fresh OS install would fix it. Then a year or so, off the farm again. I saw no error correction, had it replaced with a very similar machine, no issues. The argument was, it's only the possibility, and only once in a blue moon... The bigger the RAM, the faster we do stuff, the sooner "once in a blue moon" tends to happen. I did put that box on my personal network, and under Linux (was win NT before), seemed fine. In the syslog, after a year, there were various kernel messages, each recovered, but there was something to recover from... Win NT would blue screen a lot. That's different today with better kernel software from Microsoft, but the point is no error correction comes with no real way to understand where some trouble may have come from. And that was doing light duty stuff. Didn't trust it for a build, frankly. We get fast, quality, cheap. Pick two :D more generally, the fact that the CPU cannot know if it's transactions with RAM make any sense, unless ECC or even simple parity are present, should be a worry today. Our processes are small, clocks fast, density high. We are pushing it on all fronts! Best employ error correction. And, back in the day, the Apple 2 had no parity on its RAM, the first IBM PC did. Even those much larger, more robust circuits, clocked slowly, would throw bit errors. The IBM guys knew that from their experiences.
- Zardoz84 10y ago> I did put that box on my personal network, and under Linux (was win NT before), seemed fine. In the syslog, after a year, there were various kernel messages, each recovered, but there was something to recover from... Win NT would blue screen a lot. That's different today with better kernel software from Microsoft, but the point is no error correction comes with no real way to understand where some trouble may have come from. Haha, I remember my first steps with Linux in 1998/99. I got a faulty hard disk of 100MiB that on Windows was constantly getting errors. How ever, when I try to use it on Linux, I found that was working without any issue.