couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1218) Better logger performance
Date Tue, 12 Jul 2011 22:05:00 GMT


Paul Joseph Davis commented on COUCHDB-1218:

Also, browsing the those benchmark graphs I notice that response times aren't changing, but
the number of requests per second is increasing. Have you looked at memory usage patterns
during such a test? I'd be curious to see of the disk_log process is just being out competed
by .couch file i/o and then it buffers the log messages in RAM. Not that I have any idea how
bad that'd be in terms of size.

> Better logger performance
> -------------------------
>                 Key: COUCHDB-1218
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Filipe Manana
>            Assignee: Filipe Manana
>         Attachments: 0001-Better-logger-performance.patch
> I made some experiments with OTP's disk_log module (available since 2001 at least) to
use it to manage the log file.
> It turns out I got better throughput by using it. Basically it adopts a strategy similar
to the asynchronous couch_file Damien described in this thread:
> Here's a benchmark with relaximation, 50 writers, 100 readers, documents of 1Kb, delayed_commits
set to false and 'info' log level (default):
> The reads got a better throughput (bottom graph, easier to visualize).
> The patch (also attached here), which has a descriptive comment, is at:

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message