couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Miles Fidelman <>
Subject Re: Why are reads from CouchDB so slow? (1.5MB/s or thereabouts)
Date Fri, 23 Mar 2012 13:17:41 GMT
Jonathan Williamson wrote:
> Also the result of:
> time curl http://localhost:5984/>  /dev/null
> real	0m0.011s
> user	0m0.000s
> sys	0m0.000s
> Suggests the overhead to be around 0.01 seconds.
> Whereas to fetch a single document (700k in size):
> time curl http://localhost:5984/[dbname]/[documentid]>  /dev/null
> real	0m0.296s
> user	0m0.010s
> sys	0m0.010s

Since you're measuring the end-to-end time of a client-server 
transaction, there are two additional components to the real-time number:
- time consumed while other things are happening
- time that is actually consumed by <> processing your request

Pretty clearly, both those numbers are tiny for the baseline 
transaction, but for the CouchDB transaction, how much of what's taking 
up elapsed time is actual processing by CouchDB, and how much of the 
time is CouchDB waiting for something else to happen?

Is there a way to profile what CouchDB does once it receives that 
request? For that matter, what kind of profiling has been done of 
CouchDB's processing chain?

Miles Fidelman

In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra

View raw message