There's another consideration on ND6.x, too, and that's that the request thread pool is round-robinned, so threads are assigned in strict order rather than being pooled to see who's busy and who's free. R5 went for the first available thread, but D6 might assign a request to a thread that is already running as fast as it can.
That has apparently been fixed (made configurable) in D6.5.5 (and one would assume, in D7.x). See EriK Brooks' posting in the ND 6&7 forum here for more:
There's another consideration on ND6.x, too, and that's that the request thread pool is round-robinned, so threads are assigned in strict order rather than being pooled to see who's busy and who's free. R5 went for the first available thread, but D6 might assign a request to a thread that is already running as fast as it can.
That has apparently been fixed (made configurable) in D6.5.5 (and one would assume, in D7.x). See EriK Brooks' posting in the ND 6&7 forum here for more:
{Link}