| |||||||||||||
The Journal - a proposed syslog replacementThe Journal - a proposed syslog replacementPosted Nov 21, 2011 19:06 UTC (Mon) by mpr22 (subscriber, #60784)In reply to: The Journal - a proposed syslog replacement by SEJeff Parent article: The Journal - a proposed syslog replacement ECC seems vanishingly unlikely to be the norm until companies are forced to do it (as in, a sufficiently-large jurisdiction's laws make it either criminal or sufficiently expensively tortious to sell end-product devices that don't use some kind of ECC technology on their memory), because it increases the design and manufacturing costs of the end product without increasing sales of the end product.
(Log in to post comments)
The Journal - a proposed syslog replacement Posted Nov 21, 2011 19:22 UTC (Mon) by SEJeff (subscriber, #51588) [Link]
Agreed. That is why filesystems which checksum and keep multiple copies of data/metadata will help paper over the problem of unreliable hardware. Things like ZFS and Btrfs truly are the future.
The Journal - a proposed syslog replacement Posted Nov 24, 2011 8:06 UTC (Thu) by cas (subscriber, #52554) [Link] because it increases the design and manufacturing costs of the end product without increasing sales of the end product. and the really annoying thing is that it would just be a short-term once-off design cost until the chipsets for various device types all had ECC support (all AMD CPU chipset motherboards have ECC support and have had for several years - the catch is that ECC RAM is much more expensive). And the economies of scale for producing just one kind of RAM instead of "server RAM" and "desktop RAM", would quickly offset even those costs within a HW design generation which is, of course, the reason why it hasn't happened - artificial market segmentation is extremely profitable. You can only charge more for "server-class" hardware if they have a few things which don't exist or are uncommon on "consumer" motherboards - e.g. ECC being uncommon outside of AMD chipsets, consumer motherboards having SATA rather than SAS (which should just replace SATA entirely), and consumer drives being SATA interface rather than SAS.
|
|||||||||||||