2 ms·
Google then had complete regret not doing this with ECC RAM: https://news.ycombinator.com/item?id=14206811 https://news.ycombinator.com/item?id=14206811
by 1970-01-01 7mo ago
Google then had complete regret not doing this with ECC RAM: https://news.ycombinator.com/item?id=14206811 https://news.ycombinator.com/item?id=14206811
- ramraj07 7mo agoIt got them to where they need to be to then worry about ECC. This is like the dudes who deploy their blog on kubernetes just in case it hits front page of new york times or something.
- JumpCrisscross 7mo ago> then had complete regret not doing this with ECC RAM Yeah, my takeaway is Google made the right choice going with non-ECC RAM so they could scale quickly and validate product-market fit. (This also works from a perspective of social organisation. You want your ECC RAM going where it's most needed. Not every college dropout's Hail Mary.)
- newmana 7mo agoA great version of this and how ex-DEC engineers saved Google and their choice of ECC RAM - inventing MapReduce and BigTable https://www.youtube.com/watch?v=IK0I4f8Rbis https://www.youtube.com/watch?v=IK0I4f8Rbis