Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com
 designates 209.85.210.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=T8O5VGxK7vqkqmlsj+QKnu0MKHkpso7FGOGTKIwwKe/dlIwGomqgMozEGbE231EC27
         l2ZHvDv/hEIRcTnQ+Thwgn6fxhMhcKouPfXLR5qPk/ztFuidI3MQIt5yeZsQBMAzmiTZ
         CKZ6CGBE5pCyjAbips7ndYQGXlna2O0rwImCo=
MIME-Version: 1.0
In-Reply-To: <4B963F0A.50601@bclary.com>
References: <4B963F0A.50601@bclary.com>
From: Paul Davis <paul.joseph.davis@gmail.com>
Date: Tue, 9 Mar 2010 11:21:40 -0500
Message-ID: <e2111bbb1003090821w67a693c0jdd88f0977032ea14@mail.gmail.com>
Subject: Re: Problems with large inline attachments with 0.11
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Bob,

Do you see the same issues when using the standalone attachments API?

Paul

On Tue, Mar 9, 2010 at 7:28 AM, Bob Clary <bob@bclary.com> wrote:
> Hey all!
>
> I've been using 0.10.1 to successfully post large inline plain text
> attachments to couchdb. Now that 0.11 supports automatic compression of
> attachments, I thought I would give it a whirl.
>
> I have two issues that I can't find in jira.
>
> 1. The cpu and memory usage is extreme for attachments in the 1M to 10M
> range. A 64bit linux vm with dual 3Ghz cpu and 3.5G will routinely peg wh=
en
> updating a document.
>
> 2. The server fails to process larger attachments. The server pegs the cp=
u
> and ram and ultimately refuses the connection.
>
> Are these known issues?
>
> Are inline attachments inappropriate here?
>
> I am using =A0http://svn.apache.org/repos/asf/couchdb/trunk Revision: 920=
758
> on Centos5 64bit
>
> Thanks,
> Bob Clary
>