On Tue, Oct 6, 2009 at 4:59 PM, John Abd-El-Malek <[email protected]> wrote: > The point I was trying to make is that the 'limit' factor as you put it is > proportional to memory usage. Given our large memory consumption in the > browser process, the numbers from the paper imply dozens of corruptions just > in sqlite memory per user.
The paper (which is great!) says that error rates are proportional to active use. How busy is the average user's system? I'll bet it's idle 99% of the time. So instead of 4000 or 8000 memory errors per year per machine, one might have 40 or 80. That's still a pretty scary number. Conclusions: 1) zfs was right: checksums are a good idea. Can we add them to sqlite? 2) isolating sqlite into its own process seems like a good idea anyway if it crashes a lot 3) congress should pass a law requiring all personal computers to use error correcting memory and mandating free replacement of DIMMs that have uncorrectable errors :-) --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
