Hi all, CouchDB uses the chunked transfer-encoding capability of HTTP/1.1 to stream _all_docs, _changes, _view and similar responses to clients. We have always sent each row of these responses in a dedicated chunk. Coalescing multiple rows into a single chunk is more efficient and yields throughput improvements of approximately 30%, but this could break clients that have implicitly relied on the row-per-chunk organization.
So — do any of you knowingly rely on this behavior? How difficult would it be to accommodate this change? Thanks, Adam P.S. more details on this topic can be found in COUCHDB-2724 and associated Pull Requests: https://issues.apache.org/jira/browse/COUCHDB-2724 https://github.com/apache/couchdb-couch-mrview/pull/22 https://github.com/apache/couchdb-chttpd/pull/38 https://github.com/apache/couchdb-mango/pull/9
