Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It really depends on your application. If you're fault tolerant, then it's irrelevant. If even a single random error will throw everything down the drain, then you'll obviously want every precaution.

Most web applications don't need that kind of protection, simply because if the page load screws up, well, the user will just hit refresh and keep going.



Well, there's a good chance the same misbehavior or error will happen again and again, until the server is rebooted. Memory errors are not necessarily transient.


The user might just hit refresh and keep going. Your customer will just go.


> Your customer will just go.

You're right, I agree. And again, I'll stress that it depends on the circumstances.

Running a dedicated server with ECC memory costs $$$. Is that client worth it or not? That's only something you can determine based on your circumstances.


ECC RAM is about 10% more expensive than regular. And RAM is typically 10% of total server hardware costs. Is 1% saving really worth risking it?

32 GB ECC: http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DE...

32 GB non-ECC: http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DE...


ECC RAM by itself might be cheap, but it goes with Xeon motherboards (1.5-2x more expensive) and Xeons (2-5x more expensive)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: