I wasn't on the list at the time, so I couldn't chip in, but any change that would result in performance increase would be good.
For that particular case I'd propose default behaviour to be totally quiet, outpiting file names to be hidden behind --files or similar switch and outputing full output to be hidden behind "--debug" or "--verbose" or similarly themed swithc with mention that on large files it does impact performance majorly :)
> Dnia 22 sierpień 2017 o 18:27 Ole Tange <tange@gnu.org> napisał(a): > > > On Tue, Aug 22, 2017 at 9:47 AM, Hubert Kowalski <h.kowalski@hakger.pl> wrote: > > > Does --line-buffer affects performance penalty mentioned in > > https://lists.gnu.org/archive/html/parallel/2017-06/msg00009.html ? > > Nope. As soon as you combine --line-buffer with something that > requires a file to be written (such as --results), then it reverts to > the old behaviour. > > There has been no discussion on the list. So it is unclear if there > are any arguments for/against the current behaviour. > > It will, however, be fairly easy to change the behaviour to any of these: > > * Keep as is > > $ parallel --results res echo ::: foo > foo > > * No output to standard output > > $ parallel --results res echo ::: foo > <<nothing>> > > * Output of the stdout filename to standard output (similar to --files) > > $ parallel --results res echo ::: foo > res/1/foo/stdout > > > /Ole