[COUCHDB-639] Make replication profit of attachment compression and improve push replication for large attachments

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.11
• Component/s: Replication
• Labels: attachments compression replication

Environment

trunk

• Assignee: Unassigned
• Reporter: Filipe David Borba Manana
• Created: 04/Feb/10 23:17
• Updated: 28/Dec/10 23:28
• Resolved: 05/Mar/10 16:39

Description

At the moment, for compressed attachments, the replication uncompresses and then compresses again the attachments. Therefore, a waste of CPU time.

The push replication is also not reliable for very large attachments (500mb + for example). Currently it sends the attachments in-lined in the respective JSON doc. Not only this requires too much ram memory, it also wastes too much CPU time doing the base64 encoding of the attachment (and also a decompression if the attachment is compressed).

The following patch (rep-att-comp-and-multipart-trunk*.patch) addresses both issues. Docs containing attachments are now streamed to the target remote DB using the multipart doc streaming feature provided by couch_doc.erl, and compressed attachments are not uncompressed and re-compressed during the replication

JavaScript tests included.

Previously doing a replication of a DB containing 2 docs with attachments of 100mb and 500mb caused the Erlang VM to consume near 1.2GB of ram memory in my system. With that patch applied, it uses about 130Mb of ram memory.

Issue Links

• incorporates: COUCHDB-163 replicate attachments without Base64 encoding