couchdb-dev mailing list archives

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


Robert Newson commented on COUCHDB-1218:

disk_log module seems a bit weird, I wonder if it's intended for this? Seems more like a binary
logger sort of thing.

The patch still goes through the gen_event server, though only to print to screen, seems a
shame that we can't remove it at all.

I'm equivocal. Logging can be improved for sure but I'm not sure this is the way. Something
pluggable might be better, for example, I'd rather send the log statements over UDP to a syslog
daemon and let it handle the writing and file rotation.

> 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