Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 48E6FF070 for ; Mon, 25 Mar 2013 20:14:08 +0000 (UTC) Received: (qmail 71356 invoked by uid 500); 25 Mar 2013 20:14:06 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 71275 invoked by uid 500); 25 Mar 2013 20:14:06 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 71266 invoked by uid 99); 25 Mar 2013 20:14:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Mar 2013 20:14:06 +0000 X-ASF-Spam-Status: No, hits=-0.6 required=5.0 tests=FROM_12LTRDOM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [91.195.24.3] (HELO mail.open.bg) (91.195.24.3) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Mar 2013 20:13:59 +0000 Received: from [78.83.22.128] (port=50172 helo=localhost.localdomain) by mail.open.bg with esmtpsa (Cipher SSL3.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) id 1UKDlw-0007Qn-Da by authid with login for ; Mon, 25 Mar 2013 22:13:36 +0200 Date: Mon, 25 Mar 2013 22:13:35 +0200 From: svilen To: user@couchdb.apache.org Subject: huge attachments - experience? Message-ID: <20130325221335.7f422cb0@svilendobrev.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.16; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org hi i need some form of synchronised storage for audio files (with some metadata). Something like 10-400Mb per attachment, 1-10 attachments per doc, overall about 1000 docs, 3000 attachments, 300G total. Now i'm using just plain filesystem but it's a pain to maintain consistency across several copies. 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). Any experiences on this? how does couchdb work in such big-files scenario? ciao svilen