From user-return-11222-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Thu Jul 01 08:24:06 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 89446 invoked from network); 1 Jul 2010 08:24:06 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Jul 2010 08:24:06 -0000 Received: (qmail 59059 invoked by uid 500); 1 Jul 2010 08:24:05 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 58834 invoked by uid 500); 1 Jul 2010 08:24:02 -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 58821 invoked by uid 99); 1 Jul 2010 08:24:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Jul 2010 08:24:01 +0000 X-ASF-Spam-Status: No, hits=4.4 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of elf2001@gmail.com designates 209.85.214.52 as permitted sender) Received: from [209.85.214.52] (HELO mail-bw0-f52.google.com) (209.85.214.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Jul 2010 08:23:53 +0000 Received: by bwz17 with SMTP id 17so1662634bwz.11 for ; Thu, 01 Jul 2010 01:23:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=br9Gw7NFNDfa5Yf4dHtW7hvzwuA4c8FSSsmNNrThgNY=; b=RZhDNKaWWViZni/75pUzRGay+79trg2lDlcnSLavBsVMKSSduZ7DWARdGd3R/z0lR/ /mZ5sSdv7Zqe3L+8xh1H2dw2QckDy8s4d4dyw7IFx91ZlTlFTI92WZdgUIE0690qcDpu mfVQLTUNi1Ey6TPcwoUo3JMftT6pBwtxUex0o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=RcSU9PPAzzaKkzmAIOkAxR6luaVXaNnu4XSiBdFsQgL3ObV4vXp6870i1hCOw4i+uk OxRsR6QzfYf7oyZB8A7hPTFkpg4ryqXCpNPmxgdoI56sXj3yaN965KtJ49zyU+8UzmFa RkSKABXmwzqNXe/BqC4NRK65MO5PChC2cAtnA= MIME-Version: 1.0 Received: by 10.204.48.67 with SMTP id q3mr4908687bkf.153.1277972613149; Thu, 01 Jul 2010 01:23:33 -0700 (PDT) Received: by 10.204.100.5 with HTTP; Thu, 1 Jul 2010 01:23:33 -0700 (PDT) In-Reply-To: References: Date: Thu, 1 Jul 2010 11:23:33 +0300 Message-ID: Subject: Re: Using CouchDB for storing binary files From: Alexey Loshkarev To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=0016e6d624ffa3b3a4048a4f2fdf X-Virus-Checked: Checked by ClamAV on apache.org --0016e6d624ffa3b3a4048a4f2fdf Content-Type: text/plain; charset=ISO-8859-1 I have database with small .ogg-files (about 20-80kb each). Every document consists of 1-5 attachments. There are about 2.6M documents in database. Total size is ~60GB. I have no problems with scalability from 1k to 1m of such documents. CouchDB is still up and running find (with about ~0% of everage cpu load). 2010/7/1 Sriharsha Setty > Hello CouchDB users, > > I am evaluating CouchDB as a file store for a web-application that will > store JPEG images, audio and video files with their meta-data respectively. > I wish to index these files (documents) based on the meta-data and retrieve > them when necessary. > > Does any body use CouchDB for purposes such as binary file storage and > retrieval? If yes, what are your experiences? How does such a setup scale > for huge databases (let us say tens of terabytes)? > > Thanks in advance, > harsha > -- ---------------- Best regards Alexey Loshkarev mailto:elf2001@gmail.com --0016e6d624ffa3b3a4048a4f2fdf--