From: Stewart Smith <stewart@flamingspork.com>
To: Olly Betts <olly@survex.com>, notmuch@notmuchmail.org
Subject: Re: Notmuch performance problems on OSX
Date: Tue, 16 Feb 2010 14:53:26 +1100 [thread overview]
Message-ID: <874olhbzux.fsf@willster.local.flamingspork.com> (raw)
In-Reply-To: <slrnhkvpvr.2rf.olly@msgid.survex.com>
On Fri, 15 Jan 2010 03:58:50 +0000 (UTC), Olly Betts <olly@survex.com> wrote:
> One difference between OS X and other systems is that OS X supports the
> F_FULLSYNC ioctl, and other systems don't (currently, at least AFAIK)
> and Xapian uses that if it is available to ensure that changes have
> actually made it to disk:
>
> http://trac.xapian.org/ticket/288
>
> On other systems, it uses fdatasync() or fsync(), which typically just
> ensure that the data has left the OS - it can sit in disk controller or
> drive caches for potentially seconds longer. This call happens once
> per table for every (explicit or implicit) flush on a database.
At least if you OS and file system don't hate you (e.g. XFS on Linux),
then fsync() really does flush the drive cache.
Also keep in mind that the OSX file system (HFS+) was great for
1985. It's essentially single threaded :/
--
Stewart Smith
prev parent reply other threads:[~2010-02-16 3:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 15:30 Notmuch performance problems on OSX Oliver Charles
2010-01-14 23:16 ` Carl Worth
2010-01-18 18:35 ` Oliver Charles
2010-02-09 20:46 ` Oliver Charles
2010-02-09 22:09 ` Olly Betts
2010-02-09 22:16 ` Oliver Charles
2010-01-15 3:58 ` Olly Betts
2010-02-16 3:53 ` Stewart Smith [this message]
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=874olhbzux.fsf@willster.local.flamingspork.com \
--to=stewart@flamingspork.com \
--cc=notmuch@notmuchmail.org \
--cc=olly@survex.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://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).