Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 85788 invoked from network); 14 Jan 2010 07:31:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Jan 2010 07:31:13 -0000 Received: (qmail 72387 invoked by uid 500); 14 Jan 2010 07:31:12 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 72303 invoked by uid 500); 14 Jan 2010 07:31:12 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 72293 invoked by uid 99); 14 Jan 2010 07:31:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jan 2010 07:31:12 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gcdcd-couchdb-2@m.gmane.org designates 80.91.229.12 as permitted sender) Received: from [80.91.229.12] (HELO lo.gmane.org) (80.91.229.12) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jan 2010 07:31:02 +0000 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NVKA9-00080b-TI for dev@couchdb.apache.org; Thu, 14 Jan 2010 08:30:37 +0100 Received: from dsl-63-249-119-34.static.cruzio.com ([63.249.119.34]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Jan 2010 08:30:37 +0100 Received: from rogerb by dsl-63-249-119-34.static.cruzio.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Jan 2010 08:30:37 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: dev@couchdb.apache.org From: Roger Binns Subject: Re: Objective criteria Date: Wed, 13 Jan 2010 23:30:04 -0800 Lines: 45 Message-ID: References: <661B0EA8-4CE8-435A-8175-6A4C3FBEA5E9@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: dsl-63-249-119-34.static.cruzio.com User-Agent: Thunderbird 2.0.0.23 (X11/20090817) In-Reply-To: X-Enigmail-Version: 0.95.7 Sender: news X-Virus-Checked: Checked by ClamAV on apache.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Anderson wrote: >> I know your data is on the large side and CouchDB doesn't auto-cluster Ah, the clue! I don't think my data is "large" by any measure (10 million docs, 2GB of JSON). SQLite (note *lite* in the name) doesn't break a sweat. It only occupies 40% of a DVD. Picking a random low end machine from Dell shows that they ship with a minimum of 1GB of RAM and ideally want you to buy 2GB. Something that fits in the RAM of a $350 machine from Dell is not what I would consider large! The data fits in my machine's RAM 4 times over. Can you even buy USB sticks or SD cards these days smaller than 2GB? You could fit 15 copies of my data and an operating system in the smallest SSD drives. GMail's initial quota however many years ago was 1GB. Keith Packard's email is half a million messages but 5GB of data - http://keithp.com/blogs/notmuch/ My machine has 350,000 files and directories (excluding backups which duplicate many of those multiple times over). This is a similar order of magnitude as my data set (and several times larger if counting backups). (Note I am just talking about if you constructed a database of file and directory names, information about them etc - not the contents.) My deployment plans are the opposite of clustering and partitioning as my data set is so small! I wanted to put a copy of CouchDB on each and every server and have them replicated to each other rather than dedicated networked data servers. If this kind of (trivial!) size means clustering, paritioning etc then CouchDB is not remotely appropriate for my circumstances, and probably not for people recording file and email databases. I only wish there was documentation somewhere saying what "normal" sizes are for CouchDB and expectations for them. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktOx/wACgkQmOOfHg372QS8RgCgp5/GTZCHyZG3Sf8qaZMAAppe oM8AniZXLa2tXOw78w/N29shsQqOMBWT =46bm -----END PGP SIGNATURE-----