3 ms·
https://discourse.codinghorror.com/t/to-ecc-or-not-to-ecc/3771/62 https://discourse.codinghorror.com/t/to-ecc-or-not-to-ecc/37... Interestingly, Jeff Atwood ha
by summerlight 2y ago
https://discourse.codinghorror.com/t/to-ecc-or-not-to-ecc/3771/62 https://discourse.codinghorror.com/t/to-ecc-or-not-to-ecc/37...
Interestingly, Jeff Atwood has changed his mind on ECC memory.
- pixelpoet 2y agoEven more interestingly in the comment below, apparently you can just flick on ECC for RTX 4090 cards! Extra weird is Nvidia singling out ray tracing as a use case which shouldn't use ECC... I suppose it's no biggie if a single ray goes the wrong way down the BVH, out of trillions.
- kragen 2y agoyeah, makes sense to me. it'll just result in unnecessarily antialiasing that pixel usually. unless it corrupts the definition of an object and then that object might disappear or become enormous, and probably most raytracing memory is objects, right? not rays being traced
- sufehmi 2y agoAs soon as I worked with high-load servers in the 90s, it's already clear that ECC should be the default. Intel's marketing ploy on ECC is very desctructive and have costed many parties a lot of wasted time money & resources to handle problems caused by non-ECC memory ; and Linux Torvalds is absolutely right in roasting them for this.