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: 
 <CA+arFLVP01io2MqA_sW_9DFCLWB1X-FkA4VEuDNVe_PaUn2YbQ@mail.gmail.com>
References: 
 <CA+arFLW2pd8VHFkuP-g8LvrP9im6F9GmqkeHu7sZTUUzVvQ5bQ@mail.gmail.com>
 <CAN-3CBK0rFg02nFPfmdF1+KTHNDhPuz3s0HY6NPFraDXV7vmXw@mail.gmail.com>
 <CA+arFLUJqJXEHnWxi6QPw4cENbszraT+6UyoP4b8sH12f7-Nvw@mail.gmail.com>
 <CAN-3CBJnH-BMT4c=mQjOhTZxLj67XiDGqBBatpDrtt1puYgT4Q@mail.gmail.com>
 <CA+arFLU7Ujau_=YC4d8Bn+De==bk-_kjH+VJm4oyiU8EyewNgQ@mail.gmail.com>
 <CABvT1DEhmQioARvSSMAdFbjy5WgeHjiMKfgfRum1cfVE2e1CWw@mail.gmail.com>
 <CA+arFLWyn1PpeCsjjYn4-9mr4E+u-gieD9dud0QBbgUO+7fscg@mail.gmail.com>
 <CABvT1DEk7SfKKaM9924VkP5FC453fff0y+fHj2nekQ1v33aLTg@mail.gmail.com>
 <CA+arFLU=mwp3JAsoQDB+ZZ+LjzgXL+f79-XihJs3basrpJHvZQ@mail.gmail.com>
 <CABvT1DFVvH6MLpLFbpDJZ1Nm9nOF-FYrgdXN15W8=VqaucwpZw@mail.gmail.com>
 <CA+arFLVjcAv7eiCEAGjAcAUgMz5Rqymw9cWuvqp-iB4c+we41w@mail.gmail.com>
 <CABvT1DGeAozke4gHpj9ATFKVha25RB6NiHdqsdu8NENL29Kaew@mail.gmail.com>
 <CA+arFLVP01io2MqA_sW_9DFCLWB1X-FkA4VEuDNVe_PaUn2YbQ@mail.gmail.com>
From: Jason Smith <jhs@iriscouch.com>
Date: Fri, 23 Mar 2012 12:49:26 +0000
Message-ID: 
 <CAN-3CBJ47NSGktcVXLfDSwNbp5MgAp04AoaqvaBty90ZD=YwcA@mail.gmail.com>
Subject: Re: Why are reads from CouchDB so slow? (1.5MB/s or thereabouts)
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

That is a good question. I would also like to see a performance
breakdown of where couch spends its time handling queries. Some kind
of profiler report.

On Fri, Mar 23, 2012 at 12:47 PM, Jonathan Williamson <jon@netcopy.co.uk> wrote:
> I'm not claiming a performance issue at all, I was asking why :)
>
> If they are slow for a reason then so be it, we'll find a way to work
> around it. It's clear from the testing I've done what kind of
> throughput we can get for our specific use case.
>
> On Fri, Mar 23, 2012 at 12:44 PM, Robert Newson <rnewson@apache.org> wrote:
>> I can confirm that you won't get nginx's sendfile level of
>> performance, if that helps at all. However, if we're to investigate a
>> performance issue I want to be sure that an issue has been competently
>> discovered. The minimum for me would be seeing results from a trusted
>> benchmarking tool.
>>
>> B.


-- 
Iris Couch