On Sun, May 14, 2006 at 01:24:04PM -0700, [EMAIL PROTECTED] wrote:
> not even slowdown that could be explained by typical fork overhead, it's
> literally
> 200% the difference.
>
> >From 20060313 and any snapshot above that, I see the exact same behavior.
> >From any
> below *and including* 20060309 I do *not* see the behavior.
>
> -cl
Based on looking over the diff, I'm starting to wonder if the slowdown is
primiarly
occuring due to later changes somewhere because of:
* fork.cc (fork_retry): Define.
(frok::parent): Reorganize to allow retry of failed child creation if
child signalled that it was ok to do so.
Since it now it appears to be operating in an infinite loop with breakouts.
What's
the best way of narrowing down the actual reason for slowdown? strace? Modifying
the diff to add extra debugging output specifying the amount of retries that may
have occured?
-cl
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
