Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAN-3CBK0rFg02nFPfmdF1+KTHNDhPuz3s0HY6NPFraDXV7vmXw@mail.gmail.com>
References: 
 <CA+arFLW2pd8VHFkuP-g8LvrP9im6F9GmqkeHu7sZTUUzVvQ5bQ@mail.gmail.com>
	<CAN-3CBK0rFg02nFPfmdF1+KTHNDhPuz3s0HY6NPFraDXV7vmXw@mail.gmail.com>
Date: Fri, 23 Mar 2012 11:41:36 +0000
Message-ID: 
 <CA+arFLUJqJXEHnWxi6QPw4cENbszraT+6UyoP4b8sH12f7-Nvw@mail.gmail.com>
Subject: Re: Why are reads from CouchDB so slow? (1.5MB/s or thereabouts)
From: Jonathan Williamson <jon@netcopy.co.uk>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

As I'm requesting the documents in the exact format I submitted them
(with no transformations or extra information) I'd expect something
not far off a static file request from Nginx. As far as I can tell the
.couch files aren't compressed (though that wouldn't cause such slow
performance on an i5 anyway) and appear to contain the original
documents almost "as is".

The other side effect is that while fetching the documents the CPU
usages rises to 100% which suggests, I guess, that CouchDB is reading,
deserialising, serialising, and then streaming the document. But it
doesn't seem like that should be necessary really?

On Fri, Mar 23, 2012 at 11:16 AM, Jason Smith <jhs@iriscouch.com> wrote:
> Hi, Jonathan.
>
> Can we start by identifying how fast you think **is** reasonable. What
> speeds were you expecting? And on what grounds do you base that
> expectation?
>
> (For example, perhaps connecting and fetching one row from MySQL?)