couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (Reopened) (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (COUCHDB-1218) Better logger performance
Date Tue, 17 Jan 2012 14:49:40 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Newson reopened COUCHDB-1218:
------------------------------------


The current fix was reverted due to the inability to truncate the file during external log
rotation. The performance improvements are still valuable so we should revisit this for 1.3
(and possibly backport to 1.2.1 if there is one)
                
> Better logger performance
> -------------------------
>
>                 Key: COUCHDB-1218
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1218
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Filipe Manana
>            Assignee: Filipe Manana
>             Fix For: 1.2.1, 1.3
>
>         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:
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201106.mbox/%3C5C39FB5A-0ACA-4FF9-BD90-2EBECF271850@apache.org%3E
> Here's a benchmark with relaximation, 50 writers, 100 readers, documents of 1Kb, delayed_commits
set to false and 'info' log level (default):
> http://graphs.mikeal.couchone.com/#/graph/9e19f6d9eeb318c70cabcf67bc013c7f
> The reads got a better throughput (bottom graph, easier to visualize).
> The patch (also attached here), which has a descriptive comment, is at:
> https://github.com/fdmanana/couchdb/compare/logger_perf.patch

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message