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 You're right, when a program is modified for multithreading, there can sometimes be a lot of overhead, data might need to be rearranged to be handled in parallel, there is a setup cost, and a tear-down cost in bringing the data together. Most people who write multithreaded programs gladly pay this cost in the interest of overall performance. Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org