Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 10690 invoked from network); 10 Jan 2009 04:13:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Jan 2009 04:13:48 -0000 Received: (qmail 3397 invoked by uid 500); 10 Jan 2009 04:13:47 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 3372 invoked by uid 500); 10 Jan 2009 04:13:47 -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 3361 invoked by uid 99); 10 Jan 2009 04:13:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jan 2009 20:13:47 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates 209.85.132.242 as permitted sender) Received: from [209.85.132.242] (HELO an-out-0708.google.com) (209.85.132.242) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Jan 2009 04:13:38 +0000 Received: by an-out-0708.google.com with SMTP id b2so2857601ana.5 for ; Fri, 09 Jan 2009 20:13:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=cy2XXGAshjvo+mOi0MJwildx3Y8CRfqGLE4rhu1qqlU=; b=BXLjt6kgbU4pKt8Lp2WyPlLlHBYXWqyiBTSt82Y8KjY5iE/oz0iwtrg7143bTWdq43 Eb46du+ggYVG0FOY45DdZ44L9Lwl638zmQzMXJb7nhBXxuS8OvvwW28u4kMhNRgfBq3v DRMmHX08pFrDlgRO/ZDTRU2Qr/T98hYK57Cgs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=alJoF/7ybh/CKCLo5apY85CapZXtnM37cJ3wvBJkCLcmykmU7MSz0N3M/tn77Bj/AW LkIGGAPQL1YL1czA1zZbJrGdPdOJgnbJHKe1EBwEJGU9Lz7OfYSj8NMTrvMOvYfNTJTs JaOp0Q9aRP1x7zg8Y5bWgTkSbAyA+LJVg1bzU= Received: by 10.65.233.16 with SMTP id k16mr18496369qbr.40.1231560796907; Fri, 09 Jan 2009 20:13:16 -0800 (PST) Received: by 10.65.181.8 with HTTP; Fri, 9 Jan 2009 20:13:16 -0800 (PST) Message-ID: Date: Fri, 9 Jan 2009 20:13:16 -0800 From: "Chris Anderson" To: user@couchdb.apache.org Subject: Re: Write Performance In-Reply-To: <4967E7D4.5090304@cashnetusa.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49654ACC.5070309@cashnetusa.com> <49654F15.7020803@cashnetusa.com> <49655B2D.5090509@cashnetusa.com> <4967E7D4.5090304@cashnetusa.com> X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Jan 9, 2009 at 4:12 PM, Josh Bryan wrote: > > Also, are there any major gotcha's I should be concerned about in terms > of file formats between versions. If we start importing data using the > 0.8 branch, how hard will an upgrade to 0.9 be? The reason I ask is > that I am dealing with about 300 GB of data. If the upgrade process > will require running some conversion process over the old tables, I > would like to start putting together some estimate of how much time that > will require. > The most efficient way to upgrade file-formats is via replication or dump/load, both of which work over HTTP. I'd recommend using current trunk, and then freezing to the 0.9 branch when we release it, if you want to avoid format conversions. -- Chris Anderson http://jchris.mfdz.com