On Tue, Aug 16, 2011 at 8:18 PM, John Cheng <johnlich...@gmail.com> wrote: > same kind of behavior that I've observed. It could help uncover some > unexpected performance regression in v 1.10.0.
Have you tried setting server's socket options, in the .ini config, as I suggested before? (setting nodelay to true) > > >> >> BTW, are you using the bulk-insert API or sending a separate HTTP request >> for every document? >> >> —Jens >> > > I am using a separate HTTP request for every document in every case: > > * python-couchdb API > * Traditional HttpClient API ( ThreadSafeHttpClient with a large connection > pool ) > * Async HttpClient > > I can probably get much better performance with the bulk-insert API, but I'm > not trying to do a performance benchmark here (performance benchmarks are > almost always pointless). I'm just documenting the different behaviors of > CouchDB so I have better understanding of CouchDB. > > My python-couchdb code could use a bit of optimization, starting with using > the 'batch=ok' parameter on inserts. However, that doesn't explain the > drastic performance difference between testing against CouchDB 0.10.0 and > 1.1.0. Something is wrong there and I'm not able to identify what it is. > > -- > --- > John L Cheng > -- Filipe David Manana, fdman...@gmail.com, fdman...@apache.org "Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men."
