Online BTO options for PowerMacs have both options availble. What's the difference and why are there options here when the price is significantly different.
D
D
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Non EEC Memory or EEC Memory
- Thread starter Mr. Anderson
- Start date
- Sort by reaction score
ECC - Error Correction ram. - I'd use this if I was doing sensitive work. What it means is if there is a parity in the RAM then it'll fix it. Servers use this kind of RAM same with scientists and a lot of others.Mr. Anderson said:
Non-ECC means it won't correct parity's on its own. You just have to flush the RAM (restart) or redo what you were doing to remove the parity.
Parity-checking RAM detects single bit errors.
One bit throws off a byte, one byte off everything
http://www.scl.ameslab.gov/Projects/old/ClusterCookbook/memory.html
I ordered my Power Mac with non-ecc 1GB...I might switch to ECC ram later, my windows server takes ECC ram. I can't really tell any difference.
Well you won't really. If you've had a kernel crash or that, there could have been a parity in the RAM. On PC's they won't load up if there is a parity stuck in the RAM. So things just die basically. That's why some vendors RAM works better than others, because they have a fake parity checking mechanism on the RAM.ipacmm said:
Hmmm, interesting - so this is basically so things don't crash? How about doing 3D animation - even though its computationally top heavy, its not doing continuous calculations, just trying to determine pixel colors for each rendered image.
D
D
Mr. Anderson said:
ECC chip is the chip in the centre of the ram stick
Obvioulsy not present in the Non-ECC RAM
ECC RAM is more or less a waste of time (unless you're running a server or chomp through CAD programs allday. It actually slows done RAM access times as all the data is checked for errors.
Keep in mind that up until now Apple hasn't supproted ECC RAM and life has been fine.
My advice, save your pocket and increase your speed by buying Non-ECC.
Cheers
Jordan
P.S: Indepth writeups can be found on http://www.aandtech.com, http://www.tomshardware.com etc...
I agree that, unless you're doing something super-sensitive, it's probably not worth it; it will eventually save you from an app (or OS) crash, but only VERY rarely, so it's probably not worth the added expense and slightly slower RAM for most folks.
To give a positive example, OSX's server monitor loggs errors that were caught and corrected by EEC RAM. I have an XServe with EEC RAM running at work, and in the past 6 months of 24X7 fileserver use, it has caught and fixed exactly one error.
Now, that error could've brought down the entire server, so it was worth it in this case (and there will probably be another a few months from now), but for a home computer I doubt you'll ever notice.
The 3D rendering is an interesting example of somewhere it *might* be useful; if you're running renderings that take days, it would suck terribly to have it crash near the end, and since RAM speed probably doesn't make that much difference (processor bound, after all), EEC might be a worthwhile investment since you're probably spending heaps on hardware anyway.
To give a positive example, OSX's server monitor loggs errors that were caught and corrected by EEC RAM. I have an XServe with EEC RAM running at work, and in the past 6 months of 24X7 fileserver use, it has caught and fixed exactly one error.
Now, that error could've brought down the entire server, so it was worth it in this case (and there will probably be another a few months from now), but for a home computer I doubt you'll ever notice.
The 3D rendering is an interesting example of somewhere it *might* be useful; if you're running renderings that take days, it would suck terribly to have it crash near the end, and since RAM speed probably doesn't make that much difference (processor bound, after all), EEC might be a worthwhile investment since you're probably spending heaps on hardware anyway.
Are these errors logged in non-server OS X? I am curious if I have ever been saved a crash by it.