> Quentin Rameau:
> >We are not collecting per-cpu statistics, so it's misleading at best.
>
> Maybe we should do that?
>
> From conky(1):
>
> >cpu (cpuN)
> >CPU usage in percents. For SMP machines, the CPU number can be
> >provided as an argument. ${cpu cpu0} is the total usage, and
> >${cp
> > This commit allows to specify (statically) the number of CPU's (ncpu).
> > This allows to show the cpu usage relative to 1 CPU.
> > So, when 1 cpu is busy, 100% is shown. 2 cpu's busy: 200%, and so on.
> > At this point, the configuration of ncpu is static.
> >
> > When no number is given (the
Quentin Rameau:
We are not collecting per-cpu statistics, so it's misleading at best.
Maybe we should do that?
From conky(1):
cpu (cpuN)
CPU usage in percents. For SMP machines, the CPU number can be
provided as an argument. ${cpu cpu0} is the total usage, and
${cpu cpuX} (X >= 1) are in
> This commit allows to specify (statically) the number of CPU's (ncpu).
> This allows to show the cpu usage relative to 1 CPU.
> So, when 1 cpu is busy, 100% is shown. 2 cpu's busy: 200%, and so on.
> At this point, the configuration of ncpu is static.
>
> When no number is given (the backward co
This commit allows to specify (statically) the number of CPU's (ncpu).
This allows to show the cpu usage relative to 1 CPU.
So, when 1 cpu is busy, 100% is shown. 2 cpu's busy: 200%, and so on.
At this point, the configuration of ncpu is static.
When no number is given (the backward compatible opt
