>
> Took me a while to figure out that // == "parallel" :)
>
Sorry, that's left over from Math classes :)
> I'm pretty sure (but not entirely, I'd have to check the code) that
> the request is forwarded as one request to the necessary node(s); what
>
Humm... hadn't even thought of that forwarding
>> With the slicing, I'm not sure off the top of my head. I'm sure
>> someone else can chime in. For e.g. a multi-get, they end up as
>> independent tasks.
>
> So if I multiget 10 keys, they are fetched in //, consolidated by the
> coodinator and then sent back ?
Took me a while to figure out that
Answer below
> > Pool NameActive Pending Completed Blocked
> All
> > time blocked
> > ReadStage27 2166 3565927301 0
> With the slicing, I'm not sure off the top of my head. I'm sure
> someone else can chime in. For e.g. a mult
Was't that on the 1.0 branch ? I'm still running 0.8x ?
@Peter: investigating a little more before answering. Thanks
2011/12/10 Edward Capriolo
> There was a recent patch that fixed an issue where counters were hitting
> the same natural endpoint rather then being randomized across all of them.
There was a recent patch that fixed an issue where counters were hitting
the same natural endpoint rather then being randomized across all of them.
On Saturday, December 10, 2011, Peter Schuller
wrote:
>> Pool NameActive Pending Completed Blocked
All
>> time blocked
> Pool Name Active Pending Completed Blocked All
> time blocked
> ReadStage 27 2166 3565927301 0
In general, "active" refers to work that is being executed right now,
"pending" refers to work that is waiting to be executed (go in
