Re: notification output bottleneck

On 30.08.2012 13:02, Johan Corveleyn wrote:
> But won't the output thread then take just as long, so the user still
> has to wait until that is finished? There is not much point (from the
> users perspective) in having the checkout finished after 25 minutes,
> if the output still keeps coming in for another 25 minutes...

Network I/O and WC disk operations will not be waiting for console
output, which is what's happening now; they'll both run in parallel. The
total checkout time would be reduced to whichever takes longest today,
console output or everything else. In other words, if your checkout
takes 30 minutes today, and 10 when you redirect to /dev/null, then
there's a good chance that with a separate output thread it'll take 20
minutes.

-- Brane

-- 
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download