On Tue, Aug 30, 2011 at 12:18:59PM +0200, Anders Johansson wrote:
On Tuesday 30 August 2011 11:22:15 Stefan Seyfried wrote:
Am Tue, 30 Aug 2011 01:20:35 +0200
schrieb Anders Johansson <ajh@nitio.de>:
The elapsed time (real) tells you how much time the command actually took to complete, and that dropped to less than a third
He meant to express that it is less efficient - in "number of CPU cycles spent"
Which is to be expected, as threading surely introduces some overhead.
That was exactly my point. The only interesting thing is overall time, unless you're trying to minimize power usage, which might be interesting for embedded systems, but for a general desktop system, speed and performance usually take center stage
Hi, I don't agree with that! General desktop systems still run many processes, which often include zipping/unzipping, in the background and I would *not* want these processes to use all my CPU cores with high %. For foreground/interactive processes, it can be very useful, but it's for the user to determine when (just like with make -j). I would very much prefer the default to stay the same. Mischa -- Nikhef Room H155 Science Park 105 Tel. +31-20-592 5102 1098 XG Amsterdam Fax +31-20-592 5155 The Netherlands Email msalle@nikhef.nl __ .. ... _._. .... ._ ... ._ ._.. ._.. .._.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org