3 ms·
I used to run a home Linux desktop and a home Linux server. Neither had ECC RAM. I spent something like two years trying to spot a soft error. My detector was
by tzs 12y ago
I used to run a home Linux desktop and a home Linux server. Neither had ECC RAM. I spent something like two years trying to spot a soft error.
My detector was simple. I had a process that allocated a fixed size buffer, filled it with a pattern, and then went into a loop. The loop would check to see if the pattern was undisturbed and then sleep 60 seconds.
I had this process running on both machines pretty much continuously. Neither ever detected an error in the pattern. I was a bit disappointed.
I've been using a 2008 Mac Pro at work since 2008, and a 2009 Mac Pro at home since 2009. Both have ECC RAM. I've never seen an indication that the ECC has actually had to correct anything [1].
[1] I'm not fully sure how I would see if the ECC has corrected a transient error. I've read that it would show up in the DIMM status in system profiler, but I don't check that often, so I could easily miss a transient error.
- PhantomGremlin 12y ago> Neither ever detected an error You didn't have a very big sample size. Here's what Google had to say about the topic based on their systems[1]: Our first observation is that memory errors are not rare events. About a third of all machines in the fleet experience at least one memory error per year [1] http://research.google.com/pubs/pub35162.html http://research.google.com/pubs/pub35162.html
- baruch 12y agoI don't have a fleet of systems like Google but on the several few thousand servers I look over, I see the number of ECC errors is lower than that. It is however a strong power law distribution, many servers (>70%) see no errors at all, and a few have so many that they are unusable, some are in between and have undetected performance or other impact.