The memory itself isn't all that much more expensive, but the motherboards that run it do seem to be quite a bit more expensive. Or, am I wrong about that? If not, the decision to utilize ECC memory can start to get pricey for that reason.
On the other hand, for most people, HomeSeer does run 24/7, and it's something you want to "just work" with high reliability. Therefore, you typically want to avoid crashes and hangs and other errors that might arise when bits get inadvertently flipped in memory.
If you're able to run code that has a tiny memory footprint, there's less probability of being affected. Also, a watchdog should reboot a system that crashes or hangs. So, there might be ways to dance around the problem, if it even is a problem at all. Are there software techniques that would effectively obviate the need for ECC, perhaps at some mild performance penalty?
Really, though, maybe we should start with: is it even a problem worth addressing? How would you know whether it was or wasn't? Let's be clear: commercial grade servers do use it, and so this isn't a purely theoretical question. Those in the know seem to be voting in favor of it using hard cash.
Assume HS3 either is or becomes stable enough that the question is worth considering. I can't predict what future releases may hold, but so far my current system seems solid. My "production" system (i.e. my in-use HomeSeer system) may be parked where it is for quite a while, and I'll probably use expendable systems to track the current releases and for deciding when to upgrade my production system.
Bottom line: What's a reasoned argument for utilizing ECC or not on a production HomeSeer system?
On the other hand, for most people, HomeSeer does run 24/7, and it's something you want to "just work" with high reliability. Therefore, you typically want to avoid crashes and hangs and other errors that might arise when bits get inadvertently flipped in memory.
If you're able to run code that has a tiny memory footprint, there's less probability of being affected. Also, a watchdog should reboot a system that crashes or hangs. So, there might be ways to dance around the problem, if it even is a problem at all. Are there software techniques that would effectively obviate the need for ECC, perhaps at some mild performance penalty?
Really, though, maybe we should start with: is it even a problem worth addressing? How would you know whether it was or wasn't? Let's be clear: commercial grade servers do use it, and so this isn't a purely theoretical question. Those in the know seem to be voting in favor of it using hard cash.
Assume HS3 either is or becomes stable enough that the question is worth considering. I can't predict what future releases may hold, but so far my current system seems solid. My "production" system (i.e. my in-use HomeSeer system) may be parked where it is for quite a while, and I'll probably use expendable systems to track the current releases and for deciding when to upgrade my production system.
Bottom line: What's a reasoned argument for utilizing ECC or not on a production HomeSeer system?
Comment