On Jul 28, 2010, at 3:44 AM, Ævar Arnfjörð Bjarmason wrote: > SQLite has an option to turn that off [1], but I don't know if it has > an equivalent feature to manually call fsync when you need that. The right way to use SQLite is to have a memory-packed database which you check first, and where you do al of your work. Then once you hit a stable stopping point, you commit those changes to your on-disk SQLite database, which can have proper transaction support. That way you don't lose your database when your crappy binary-only video driver crashes on you, but you don't trash your disk performance because of the fsync() calls.... It only took a few years for firefox developers to figure this out, but the next version is supposed to finally get this right.... it'll be nice to have it NOT chewing up a third of a megabyte of SSD write endurance on every URL click.... -- Ted -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html