Hacker News new | ask | show | jobs
by groundthrower 1656 days ago
Yes this is one concern. Are you sure it was a result of using non ECC mem and how did you find out it was because of that?
1 comments

We could never be absolutely sure, due to the true Heisenbug nature of the behavior, but after tons of code audits and the observation after reverse proxy traffic analysis that it only occurred on processing by the non-ECC hosts, and never on the ECC hosts, that it was the most likely culprit.

The fact that the errors were single bit errors also strongly pointed in that direction.