On Apr 2, 2009, at 1:51 PM, Luke Tucker wrote:
On Apr 1, 2009, at 1:37 PM, Paul Davis wrote:
And then last but not least is adding
concurrency to passing documents through the JS process. The last bit
is probably easiest, but most reports say that couchjs is sitting
around 30% cpu indicating its not really the bottleneck quite yet.
HTH,
Paul Davis
Does couchdb supply the couchjs process with work to do while it is
performing i/o with previous results?
Nope.
If not, I could also see this cpu utilization partially resulting
from cpu and i/o being used too serially vs. pipelined -- ie i/o may
very well be the bottleneck, but is there some room for improvement
before we're actually hitting it?
In my opinion, yes, there's quite a bit of room. I've been meaning to
code that pipelining up but haven't gotten around to it. Cheers,
Adam
