[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Default output-sync setting (was: Re: [bug #33138] .PARLLELSYNC enha

From: Frank Heckenbach
Subject: Re: Default output-sync setting (was: Re: [bug #33138] .PARLLELSYNC enhancement with patch)
Date: Sat, 04 May 2013 04:04:29 +0200

Eli Zaretskii wrote:

> > From: Paul Smith <address@hidden>
> > Cc: address@hidden
> > Date: Sun, 28 Apr 2013 22:03:39 -0400
> > 
> > Now that we seem to have a workable solution for output synchronization
> > for both POSIX and Windows systems, I wonder if we shouldn't consider
> > enabling it as the default mode when parallel builds are running.
> I don't think we should do this unless users demand it, which means we
> should wait for the next release and some time beyond before making
> the decision.

I don't have strong opinions on the default setting. Though I hope
the feature will be visibly announced with the next release, so
users get to know about it and hopefully some will try it.

> FWIW, I'm running 8-way parallel Make jobs for many months now, and
> never had any trouble interpreting their output, neither when they
> succeed, nor when they don't.

FWIW, what annoyed me most was the lack of realiable directory
information. (Not like I wasn't able to locate the offending files
myself, but I'd rather let my computer do it for me and just point
me to the error position in my editor.) This is now fixed by the,
sometimes redundant, enter/leave messages. The actual output-sync
was a precondition to make them work.

> The synchronized output operation annoys me slightly in that there are
> distinct time intervals when Make says nothing at all, and then the
> output appears in large chunks that get dumped en-masse to the
> screen.  IOW, the user experience is different and takes time to get
> used to.

Yes, it's different, but I'm a bit surprised it's *so* different to
you. In my case, I hardly notice the extra delay (and I do watch the
output while it's running, usually starting to fix my first errors
while the rest is compiling). Of course, I'm using the minimal sync
("-O job"). If you tried with especially "-O make", the delays may
be much longer, depending on your make file hierarchy. (I know it's
the case with mine, that's why I implemented the finer sync modes

reply via email to

[Prev in Thread] Current Thread [Next in Thread]