I would be interested to see the time of the same benchmark in Javascript for the browser (where it can use its connection pool).
You have a fork/exec + TCP connection overhead for each iteration. That may or may not be relevant to your particular use case. On Fri, Mar 23, 2012 at 12:36 PM, Jonathan Williamson <[email protected]> wrote: > It was just a script that looped over the keys for 1000 documents, > fetching them one after another (using curl). > > On Fri, Mar 23, 2012 at 12:31 PM, Robert Newson <[email protected]> wrote: >> Using which http benchmarking tool (and exactly which settings)? >> >> On 23 March 2012 12:30, Jonathan Williamson <[email protected]> wrote: >>> My initial CouchDB test was over 1000 GETs (all to roughly similar >>> documents), taking an average of the total time vs the total amount of >>> data recieved. >>> >>> On Fri, Mar 23, 2012 at 12:26 PM, Robert Newson <[email protected]> wrote: >>>> Are you really extrapolating mb/s from a single curl command? -- Iris Couch
