[
https://issues.apache.org/jira/browse/COUCHDB-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064518#comment-13064518
]
Filipe Manana commented on COUCHDB-1218:
----------------------------------------
I tried something hand crafted, like the async couch_file does, before and the
results were not as good as with disk_log:
http://friendpaste.com/X9tX1LCb9Mn6SiTueFlXY
Unless there's a high cpu or memory usage risk (or high chances of losing
messages), I don't see a problem in using disk_log - if it's part of standard
OTP, it's available in every installation, plus we get the benefits of wide
exposure (testing, bug fixes, enhancements)
> 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
> 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/%[email protected]%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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
