From: Theodore Tso <tytso@mit.edu>
Date: Wed, 28 Jul 2010 11:08:37 GMT
Subject: Re: inotify daemon speedup for git [POC/HACK]
Message-ID: <5C87954A-5BB2-468D-8C4E-79A97685ED0D@mit.edu>
In-Reply-To: <AANLkTinuq9Q_RADtQwvVTn-kDCw7cg7JcdkhbQnek9Tw@mail.gmail.com>


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