SLUG Mailing List Archives
Re: [SLUG] copying binaries from one Centos to another?
- To: slug@xxxxxxxxxxx
- Subject: Re: [SLUG] copying binaries from one Centos to another?
- From: Daniel Pittman <daniel@xxxxxxxxxxxx>
- Date: Sat, 18 Sep 2010 19:17:59 +1000
- Reply-to: slug@xxxxxxxxxxx
- User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
"Voytek Eymont" <lists@xxxxxxxxxx> writes:
> On Sat, September 18, 2010 3:37 pm, Daniel Pittman wrote:
>> "Voytek Eymont" <lists@xxxxxxxxxx> writes:
>> That will not help unless you rebuild Cacti to use the older version of
>> RRDTool. (Also, are you /sure/ it is RRDTool and not something else in the
>> Cacti stack that causes the performance problems? RRDTool is
>> crazy-efficient, so I wouldn't pick it as the first point to suspect.
>> OTOH, if you measured it and found it was the cause then you measured it
>> and all. :)
> Cacti has a setup screen where path to binaries like rddtool can be entered;
That should be sufficient, then, to use your custom version.
> I thought the issue was again lack of math co-pro, and, will 'go way' on
> the P4, initially
Yeah, and naturally it didn't because there isn't anything Intel make that
doesn't have a nicely fast math coprocessor these days (and, in fact, you have
to go back to the days of the i486 to get something that didn't ship one
on-die and all... :)
> Cacti was using RRDTool 1.2x, then after a yum update, it got 1.4, I 'fixed'
> the path in setup, but, a screen draw is painfully slow now, based on what I
> found on the Celeron system, it seems it's similar issue
A screen draw? Are you running X locally on the system, or is this on your
client? Neither one necessarily points to RRD 1.2 vs 1.4, although it could
be involved in either.
✣ Daniel Pittman ✉ daniel@xxxxxxxxxxxx ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons