couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens Alfke <>
Subject Re: huge attachments - experience?
Date Mon, 25 Mar 2013 21:44:07 GMT

On Mar 25, 2013, at 1:13 PM, svilen <<>>

As i don't really need more than 1 version back, i'm playing with idea
of using couchdb for that. Either putting the files as attachments, or
if not possible, using it as filesystem-miming synchronised metadata,
with appropriate listeners reacting on changes (like rename, mv, etc).

This may get slow. CouchDB stores the attachment inside the database file, so every time the
database is compacted, all the still-valid attachments have to be copied over to the new file.
(And if you don’t compact the database, you end up using space for every version of every

TouchDB stores attachments as separate files in the filesystem. This means they don’t get
copied. It stores them as files named after their SHA-1 digests, which also means you get
some deduplication: if the database has multiple attachments with identical bodies, only one
copy is stored.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message