On Fri, Nov 18, 2016 at 2:55 PM, ianseeks wrote:

...

After that top showed those cpu lod of kwin_x11 106% cpu load it printed out 106%? How does that work? :o)

you tell me. thats how top printed it. but seriously more than one core on multicore machine. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

ianseeks wrote:

106%? How does that work? :o)

--- When you calculate cpu-time/real-time -- using the same formula that was used for years before Microsoft started automatically dividing it by the variable # of CPU's. An easy way to see it -- "time" something in bash and have TIMEFORMAT show you the "%P" (cpu/real) number, by setting TIMEFORMAT to something like:

export TIMEFORMAT="%2Rsec %2Uusr %2Ssys (%P%% cpu)"

Then run a parallel load:

time bash -c 's=999999;i=s;while ((--i));do : ; done& i=s; while ((--i));do :;done& wait' 4.03sec 8.01usr 0.00sys (199.06% cpu)

Basically, %CPU = 100*cpu time/real time You get >100 % when your program is multithreaded and using more than 1 cpu. Using 100%="N" cpu's is not very useful since when on a 100-core intel chip, a wedged, single-threaded program will show 1% cpu usage. Nice way to hide busy programs... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

ianseeks wrote:

...

106%? How does that work? :o)

--- When you calculate cpu-time/real-time -- using the same formula that was used for years before Microsoft started automatically dividing it by the variable # of CPU's.

An easy way to see it -- "time" something in bash and have TIMEFORMAT show you the "%P" (cpu/real) number,

by setting TIMEFORMAT to something like:

...

export TIMEFORMAT="%2Rsec %2Uusr %2Ssys (%P%% cpu)"

Then run a parallel load:

...

time bash -c 's=999999;i=s;while ((--i));do : ; done& i=s; while ((--i));do :;done& wait' 4.03sec 8.01usr 0.00sys (199.06% cpu)

Basically, %CPU = 100*cpu time/real time You get >100 % when your program is multithreaded and using more than 1 cpu.

Using 100%="N" cpu's is not very useful since when on a 100-core intel chip, a wedged, single-threaded program will show 1% cpu usage.

Nice way to hide busy programs...

On Saturday, 19 November 2016 14:52:55 GMT L. A. Walsh wrote: thanks... -- opensuse:tumbleweed:20161118 Qt: 5.7.0 KDE Frameworks: 5.28.0 KDE Plasma: 5.8.3 kwin5-5.8.3-168.1.x86_64 kmail5-16.08.3-1.1.x86_64 Kernel: 4.8.8-1-default Nouveau: 1.0.13_2.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2016-11-19 11:26, ianseeks wrote:

...

On Friday, 18 November 2016 15:05:40 GMT cagsm wrote:

...

On Fri, Nov 18, 2016 at 2:55 PM, ianseeks wrote:

...

...

After that top showed those cpu lod of kwin_x11 106% cpu load it printed out

106%? How does that work? :o)

you tell me. thats how top printed it. but seriously more than one core on multicore machine.

That was going to be my guess but it should really only show a max of 100% no matter how many cores.

No, if you have four cores it can go to 400%, so that you see how many cores are going full load. If you see a process at 200% you know that it is using several cores, it is a threaded process. Ok, that makes sense but makes a machine running at greater than 100% look weird especially when you try to explain than anything over 100% is impossible. I would have thought in my little world it should probably split

On Monday, 21 November 2016 13:56:56 GMT Carlos E. R. wrote: the cores and give a rating for each one or does a core get used upto 100% before it utilises another core? -- opensuse:tumbleweed:20161119 Qt: 5.7.0 KDE Frameworks: 5.28.0 KDE Plasma: 5.8.3 kwin5-5.8.3-168.1.x86_64 kmail5-16.08.3-1.1.x86_64 Kernel: 4.8.8-1-default Nouveau: 1.0.13_2.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2016-11-22 10:39, ianseeks wrote:

...

...

No, if you have four cores it can go to 400%, so that you see how many cores are going full load. If you see a process at 200% you know that it is using several cores, it is a threaded process.

Ok, that makes sense but makes a machine running at greater than 100% look weird especially when you try to explain than anything over 100% is impossible. I would have thought in my little world it should probably split the cores and give a rating for each one or does a core get used upto 100% before it utilises another core?

The display can show the load per cpu core, and that one can't go over 100%. It is the combined display which can go to number_of_cores * 100%.

If the combined graph is adjusted so that the max is 100%, then a job that is running at 100% on an eight core cpu will display at 12.5%, so that you don't see anything wrong.

A single threaded job can jump from one core to another, so that you see an average load on each core quite low, while the task itself goes at 100%. Or it can be stuck to the same core for long, and it shows in graphs.

A multi-threaded job can spread itself simultaneously on several cores, and can go to 100% on all of them. And if it is not busy, then it almost doesn't register in the graphs.

On Tuesday, 22 November 2016 13:25:41 GMT Carlos E. R. wrote: thanks -- opensuse:tumbleweed:20161120 Qt: 5.7.0 KDE Frameworks: 5.28.0 KDE Plasma: 5.8.3 kwin5-5.8.3-168.1.x86_64 kmail5-16.08.3-1.1.x86_64 Kernel: 4.8.8-1-default Nouveau: 1.0.13_2.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org