Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 78921 invoked from network); 26 Oct 2009 19:31:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Oct 2009 19:31:15 -0000 Received: (qmail 9389 invoked by uid 500); 26 Oct 2009 19:31:14 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 9329 invoked by uid 500); 26 Oct 2009 19:31:14 -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 9316 invoked by uid 99); 26 Oct 2009 19:31:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Oct 2009 19:31:14 +0000 X-ASF-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of anothernetfellow@gmail.com designates 209.85.218.217 as permitted sender) Received: from [209.85.218.217] (HELO mail-bw0-f217.google.com) (209.85.218.217) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Oct 2009 19:31:10 +0000 Received: by bwz9 with SMTP id 9so7194274bwz.32 for ; Mon, 26 Oct 2009 12:30:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=qBKEMiRdaM3uxtiafMQHso8nMqb52sZm3PqjluzLrIw=; b=R/Nonx0zBycDT5WWXuNFzrmbzuelzVmVeYO4fHMk+0jeXDmWzLXbM9tWDKmNv9XH9m UHpkMn4DQ5cRWH8QHdqOEM5g5nqNShq0vTYd0AQVTFytLAubvS70IuBv90qcNDgRt89F 9i6m/urQoBGVJNVaVMfB8fyhIMm9R49QCPA1M= 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=DnVqmeGjmZHbtD4wN25dg+E5oFIDcaZov012K/NH7v4EXTMLm74xRsVubXU9OwqAIB 8LdBQYqfmOGy0n1jEKqzII9dKympKfRfAgYJKsaP0zx8DNSSjRS4PIF0brjDKtLei+oU lGydV62l+ry27jU8pmmxuMr++XnOvSoN/07yM= MIME-Version: 1.0 Received: by 10.103.76.29 with SMTP id d29mr247051mul.50.1256585448177; Mon, 26 Oct 2009 12:30:48 -0700 (PDT) In-Reply-To: References: <58CDA2A5-54C4-44DF-88A6-DCD075CC8B91@apache.org> <23ce85920910260949g65380ab0y2803f375b1d063aa@mail.gmail.com> Date: Mon, 26 Oct 2009 20:30:47 +0100 Message-ID: <23ce85920910261230y2702dbdcp2213f0d259a1c119@mail.gmail.com> Subject: Re: Best practice for spreading one master across several disks? From: AnotherNetFellow To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=0016e65aeed044c0120476db99cb --0016e65aeed044c0120476db99cb Content-Type: text/plain; charset=ISO-8859-1 Oh, sorry Adam, I wasn't told you're one of project developers/managers. Thankyou for your reply. Jan: yes, it could be another type of use. It's, we could say, load balancing. But think, and Adam seems confirming this, that another important feature of non relational dbms is the ability to scale in size, without limits (and a single server's capacity is a limit). Giorgio 2009/10/26 Jan Lehnardt > > On 26 Oct 2009, at 17:49, AnotherNetFellow wrote: > > It seems an unofficial patch, isn't it? >> > > couchdb-lounge is a full third party project on top of CouchDB, not a > patch. > > > > The CouchDB description states that it is a distributed db. So shouldn't >> it >> integrate a distribution engine to spare databases on many servers? >> > > There are different understandings of "distributed". CouchDB's idea is that > distributing full data sets between nodes is an equally valid use-case (and > IMHO a much more common one). > > That said, Adam already said CouchDB will have partitioning and it's > a good thing :) > > Cheers > Jan > -- > > > > > >> Thankyou >> >> 2009/10/26 Adam Kocoloski >> >> On Oct 26, 2009, at 10:50 AM, Coffman, Timothy A wrote: >>> >>> I am collecting information and doing some proofs-of-concept in >>> >>>> preparation for suggesting CouchDB as a replacement for a 20-year-old >>>> house-developed document system. One topic I will need to address goes >>>> like this: >>>> >>>> (1) How big can one CouchDB database file get? >>>> >>>> >>> Unlimited, although performance will get ugly once the indexes don't fit >>> in >>> RAM. >>> >>> >>> (2) How could I store one CouchDB logical database across multiple disks >>> >>>> or machines? >>>> >>>> >>> Multiple disks: RAID >>> >>> Multiple machines: CouchDB-Lounge (not yet fully 0.10 compatible, but >>> they're working on it) >>> >>> http://tilgovi.github.com/couchdb-lounge/ >>> >>> Best, Adam >>> >>> >>> >> >> -- >> -- >> AnotherNetFellow >> Email: anothernetfellow@gmail.com >> > > -- -- AnotherNetFellow Email: anothernetfellow@gmail.com --0016e65aeed044c0120476db99cb--