From: Theodore Tso <tytso@MIT.EDU>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Avery Pennarun <apenwarr@gmail.com>,
Joshua Juran <jjuran@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Finn Arne Gangstad <finnag@pvv.org>,
git@vger.kernel.org
Subject: Re: inotify daemon speedup for git [POC/HACK]
Date: Wed, 28 Jul 2010 07:08:37 -0400 [thread overview]
Message-ID: <5C87954A-5BB2-468D-8C4E-79A97685ED0D@mit.edu> (raw)
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
next prev parent reply other threads:[~2010-07-28 11:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 12:20 inotify daemon speedup for git [POC/HACK] Finn Arne Gangstad
2010-07-27 23:29 ` Avery Pennarun
2010-07-27 23:39 ` Joshua Juran
2010-07-27 23:51 ` Avery Pennarun
2010-07-28 0:00 ` Shawn O. Pearce
2010-07-28 0:18 ` Avery Pennarun
2010-07-28 1:14 ` Joshua Juran
2010-07-28 1:31 ` Avery Pennarun
2010-07-28 6:03 ` Sverre Rabbelier
2010-07-28 6:06 ` Jonathan Nieder
2010-07-28 7:44 ` Ævar Arnfjörð Bjarmason
2010-07-28 11:08 ` Theodore Tso [this message]
2010-07-28 8:20 ` Nguyen Thai Ngoc Duy
2010-08-13 17:53 ` Enrico Weigelt
2010-07-28 13:09 ` Jakub Narebski
2010-07-28 13:06 ` Jakub Narebski
2010-08-13 17:58 ` Enrico Weigelt
2010-07-27 23:58 ` Sverre Rabbelier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5C87954A-5BB2-468D-8C4E-79A97685ED0D@mit.edu \
--to=tytso@mit.edu \
--cc=apenwarr@gmail.com \
--cc=avarab@gmail.com \
--cc=finnag@pvv.org \
--cc=git@vger.kernel.org \
--cc=jjuran@gmail.com \
--cc=jrnieder@gmail.com \
--cc=spearce@spearce.org \
--cc=srabbelier@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).