couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joan Touzet (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-271) preventing compaction from ruining the OS block cache
Date Sat, 26 Jan 2013 14:25:12 GMT


Joan Touzet commented on COUCHDB-271:

Recommend pushing this farther out, this is non-trivial, rnewson's suggestion is massively

This is not a good candidate for a (soon now!) 1.3.0.
> preventing compaction from ruining the OS block cache
> -----------------------------------------------------
>                 Key: COUCHDB-271
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>    Affects Versions: 0.8.1, 0.9
>            Reporter: Jan Lehnardt
>             Fix For: 1.3
> Adam Kocolosk:
> Hi, I've noticed that compacting large DBs pretty much kills any filesystem caching benefits
for CouchDB.  I believe the problem is that the OS (Linux 2.6.21 kernel in my case) is caching
blocks from the .compact file, even though those blocks won't be read again until compaction
has finished.  In the meantime, the portion of the cache dedicated to the old DB file shrinks
and performance really suffers.
> I think a better mode of operation would be to advise/instruct the OS not to cache any
portion of the .compact file until we're ready to replace the main DB.  On Linux, specifying
the POSIX_FADV_DONTNEED option to posix_fadvise() seems like the way to go:
> This link has a little more detail and a usage example:
> Of course, POSIX_FADV_DONTNEED isn't really available from inside the Erlang VM.  Perhaps
the simplest approach would be to have a helper process that we can spawn which calls that
function (or its equivalent on a non-Linux OS) periodically during compaction?  I'm not really
sure, but I wanted to get this out on the list for discussion.  Best,

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message