[
https://issues.apache.org/jira/browse/COUCHDB-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004320#comment-13004320
]
Jan Lehnardt commented on COUCHDB-1084:
---------------------------------------
Relaximation r/w test on a Mac Mini with a spinning disk, relaximation and
CouchDB on different machines on switched GigE ethernet.
http://graphs.mikeal.couchone.com/#/graph/698bf36b6c64dbd19aa2bef63400478c
A little less improvement, but definitely not worse. Damien says with database
files larger than available ram, the impact should be bigger. If anyone can set
up a test run like that, that'd be cool :)
> Remove unnecessary btree lookup inside couch_db_updater
> -------------------------------------------------------
>
> Key: COUCHDB-1084
> URL: https://issues.apache.org/jira/browse/COUCHDB-1084
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core
> Affects Versions: 1.2
> Reporter: Damien Katz
> Assignee: Damien Katz
> Attachments: remove_btree_lookup.patch
>
>
> The CouchDB update process has an unnecessary btree lookup, where it reads
> the values in bulks, checks for conflicts, writes the docs to disk, updates
> the values appropriately and writes them to the btree out in a second step.
> It's possible to avoid this second step, and instead do all the checking, doc
> writing and value transformation in a single btree lookup, thereby reducing
> the number of btree traversals and disk IO.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
