3 ms·
Integrity of your data. Without ECC data in memory can become corrupted at any point. It's usually just a single bit but say you are working with images, do yo
by copx 9y ago
Integrity of your data. Without ECC data in memory can become corrupted at any point.
It's usually just a single bit but say you are working with images, do you care if a single pixel changes its RGB value because of a memory error? A character in the metadata?
I do.
Unfortunately there is a hardware cartel which deliberately limits ECC to enterprise / server products so that they can inflate the price / their profit margin.
ECC RAM is more expensive to manufacture than non-ECC RAM but the price difference would be fairly minimal if ECC RAM were used everywhere - as it should.
- devwastaken 9y agoAlso any form of file that is easy to corrupt to a non-decodable state. Such as any binary save/config file, or any sort of file conversion or transferance. The data you transfer from location to location will always pass through memory, and in the case of converting that data to another format, it may not be possible to validate the destination format in relation to the original data. Hypothetically, even with hash checks when transferring files, if the chunk of data read from the source file changes, that data will be used to calculate the hash sum, along with being written to the destination file. Meaning the hash sum would match the destination file anyways. You could even get wrong hash sums and think the transfer was wrong. Really when memory can just 'change', anything can happen and there's no real good ways to get around it. ECC memory should just be everywhere.