Bug#419948: munin: stark cpu increase sarge-etch

[Jean-Michel Vourgère]

Control: noowner -1

Hi

Is that ok if I close that report now?

The explanation at https://bugs.debian.org/419948 is quite complete
about possible optimisations, and sarge is long gone.

Or do you still have issues with rrd?

-- 
Nirgal

Bug#419948: munin: stark cpu increase sarge-etch

[Florian Schlichting]

Hi Tore,

thanks for your quick reply.

   It is done by RRDtool.  Could you try downgrading librrds-perl to the
  Sarge version, or trying to nice only the munin-graph subprocess, to
  make sure it's the graphing that eats resources?  Edit
  /usr/bin/munin-cron to do that.

I can confirm that it's the call to munin-graph that consumes most of
the resources, with a tiny amount (say, 1/10th) consumed by munin-html

downgrading librrds-perl to oldstable indeed brings CPU back to pre-etch 
levels. Interestingly, this doesn't just pertain to nice cycles, but
also more than halves system cycles.

Regards,
Florian



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#419948: munin: stark cpu increase sarge-etch

[Tore Anderson]

reassign 419948 librrds-perl
quit

* Florian Schlichting


downgrading librrds-perl to oldstable indeed brings CPU back to
pre-etch levels. Interestingly, this doesn't just pertain to nice
cycles, but also more than halves system cycles.


  Okay, in that case there's nothing I can do really.  Reassigning to
 librrds-perl.

Regards
--
Tore Anderson


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#419948: munin: stark cpu increase sarge-etch

[Tore Anderson]

* Florian Schlichting

updating a stable server from sarge to etch, the amount of CPU munin 
uses presumably for graphing has increased 4- or 5-fold. Please see 
attached graph (I nice'd the cronjob, all other services run with 
normal priority).


While we all know that new software always needs more resources, I
think this is a bit gross, especially given that it's the same amount
of graphs that look absolutely the same.

I realize that the actual graphing is not done by munin, but I'm not 
sure exactly where all these CPU cycles are spent, so please reassign

if appropriate.


  It is done by RRDtool.  Could you try downgrading librrds-perl to the
 Sarge version, or trying to nice only the munin-graph subprocess, to
 make sure it's the graphing that eats resources?  Edit
 /usr/bin/munin-cron to do that.

Regards
--
Tore Anderson


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#419948: munin: stark cpu increase sarge-etch

[Florian Schlichting]

Package: munin
Severity: normal

updating a stable server from sarge to etch, the amount of CPU munin
uses presumably for graphing has increased 4- or 5-fold. Please see
attached graph (I nice'd the cronjob, all other services run with
normal priority).

While we all know that new software always needs more resources, I think
this is a bit gross, especially given that it's the same amount of
graphs that look absolutely the same.

I realize that the actual graphing is not done by munin, but I'm not
sure exactly where all these CPU cycles are spent, so please reassign if
appropriate.






munin-cpu_usage_increase.png
Description: PNG image