[
https://issues.apache.org/jira/browse/COUCHDB-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14637629#comment-14637629
]
ASF subversion and git services commented on COUCHDB-2724:
----------------------------------------------------------
Commit 083d1a53c44c904d7ca0ebc9f45649f8b3342ecc in couchdb-couch-mrview's
branch refs/heads/2724-chunked-buffering from [~kocolosk]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-couch-mrview.git;h=083d1a5 ]
Buffer rows to reduce number of chunks
This patch reduces the number of chunks in an HTTP chunked response body
by coalescing multiple rows into a single transmission. The default
value is chosen to fill a standard Ethernet frame and can be configured
by setting
[httpd]
chunked_response_buffer = 1490
Setting the buffer size to 0 restores the original behavior of sending
each row in a separate chunk. Note that the same setting is several
streaming responses (e.g. _changes, _all_docs, _views).
COUCHDB-2724
> Batch rows in streaming responses to improve throughput
> -------------------------------------------------------
>
> Key: COUCHDB-2724
> URL: https://issues.apache.org/jira/browse/COUCHDB-2724
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Database Core, HTTP Interface
> Reporter: Adam Kocoloski
> Assignee: Adam Kocoloski
>
> [~tonysun83] showed me some profiling of the {{_changes}} feed which
> indicated that the coordinator process was spending about 1/3 of its time
> executing inside {{send_delayed_chunk}}. We can reduce the number of
> invocations of this function by buffering individual rows until we reach a
> (configurable) threshold for sending the data out the wire.
> We'll of course want to be careful about continuous feeds; if we're in the
> "slow drip" portion of the feed we'll obviously want to emit right away
> instead of adding latency unnecessarily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
