From: racin@free.fr
To: Jameson Rollins <jrollins@finestructure.net>
Cc: Notmuch list <notmuch@notmuchmail.org>
Subject: Re: please eat my data!
Date: Mon, 12 Apr 2010 16:41:21 +0200 (CEST) [thread overview]
Message-ID: <457171623.7414151271083281537.JavaMail.root@zimbra1-e1.priv.proxad.net> (raw)
In-Reply-To: <87tyrgeopc.fsf@servo.finestructure.net>
----- "Jameson Rollins" <jrollins@finestructure.net> a écrit :
> On Mon, 12 Apr 2010 15:33:35 +0200, "Sebastian Spaeth"
> <Sebastian@SSpaeth.de> wrote:
> > fsync is really killing xapian (and notmuch). What suffers, are the
> > boolean prefixes (tag, id, and thread). Using libeatmydata (which
> > disables fsync) shows a 10x speedup for tagging. The speedup is
> only
> > factor 2 for e.g. from: searches. This is ext4 on recent stock
> > Ubuntu. Given that search by tag and thread are performed really
> often
> > (each time I advance a thread, for example), that really hurts.
>
> Wow, this is really interesting, Sebastian. For those of us not in
> the
> know, can you explain what libeatmydata is and how it's used? It
> sounds
> like something I would *not* want to use! So you didn't have to
> recompile here, and only had to set LD_PRELOAD=./libeatmydata.so? Is
> there any drawback to what you're doing here?
>
> jamie.
>
It seems like it is a small library that implements fsync as no-op. Using LD_PRELOAD
allows to overloads the libc's fsync definition by libeatmydata's one. Making writes faster,
but no longer crash-safe.
Matthieu
next prev parent reply other threads:[~2010-04-12 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 13:33 please eat my data! Sebastian Spaeth
2010-04-12 14:21 ` Jameson Rollins
2010-04-12 14:41 ` racin [this message]
2010-04-12 15:24 ` Sebastian Spaeth
2010-04-12 17:14 ` Stewart Smith
2010-04-12 17:47 ` Dirk Hohndel
2010-04-12 23:10 ` Servilio Afre Puentes
2010-04-12 23:35 ` Dirk Hohndel
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: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=457171623.7414151271083281537.JavaMail.root@zimbra1-e1.priv.proxad.net \
--to=racin@free.fr \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.org \
/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://yhetil.org/notmuch.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).