Konstantin, What happens when you set delayed_commits to true? With that off you are requiring an fsync (iirc) after every value written and then are at the mercy at your disks write performance (but not in the sense of burst-write as these are individual, disparate write requests coming in).
Also, is this build Couch Single Server from Couchbase or some other Windows build of Couch? -R On Tue, Oct 25, 2011 at 4:03 PM, Konstantin Cherkasoff < [email protected]> wrote: > *** crossposted to [email protected] > > Hi! > > I installed CouchDB 1.1.0 on Windows (Winows 7, 32 bit) and tried to > test performance using ab.exe(Apache Benchmark > http://httpd.apache.org/docs/2.2/programs/ab.html) > ab.exe -k -c 1 -n 1000 -p ab.json -T "application/json" > http://localhost:5984/bench > where ab.json contains the simplest document {"value": "test"}. > This utility do 1000 POSTs with no concurency (-c 1) in single > connection (-k for keepalive). > On my laptop (it's NOT low cost netbook) I got 10 requests per > second.So it is 0.1 second per single request.And CPU and HDD > utilization is actually ZERO. > I was just wondering what exactly CouchDB doing all this time (0.1 > second) with single little record?As the utilization of CPU and HDD is > 0%, I believe that they are not the bottleneck. > > So where is bottleneck? > > > P.S.All test I did with delayed_commits = false.And I tried > socket_options = [{nodelay, true}] > > -- > Konstantin Cherkasoff >
