Cacti Limitations

doublek · Post by **doublek** » Thu Apr 06, 2006 1:34 am

Here we go:

-For the last 3 weeks we have been confguring cacti to pull from over 350 devices with ~

SYSTEM STATS: Time:160.5750 Method:cactid Processes:1 Threads:30 Hosts:242 HostsPerProcess:242 DataSources:48020 RRDsProcessed:18234

This is only 1/6 of the request we will be pulling for now but we are starting to run into iteresting situations.

Once we hit 65k RRDs processed (with 1/2 pulls) we hit the timout limitations using cactid.

I've increased the Threads per Process anywhere from 15 - 256, Maximum pollers from 1 - 10 and even the php.ini to 512 for mem, with the same results running on FreeBSD.

In debug mode I notice the threads run first then the mysql updates and finaly the rrdtool updates. I beleive each of the rrdtool update are ran 1 at a time from the poller.php. If wrong let me know.

We are looking into rewriting part of the scripts and if anyone is interested in the results let me know.

Post by **rony** » Thu Apr 06, 2006 10:00 am

Email TheWitness, he will help you out. He is the developer responsible for the poller.

But, I do have a question, how much memory is in this server? How many and the speed of the CPU's are there?

doublek · Post by **doublek** » Thu Apr 06, 2006 11:59 am

Were currently running dual 2.8Ghz with 4 Gig of RAM.

Post by **TheWitness** » Thu Apr 06, 2006 8:45 pm

Somehow this situation sounds familiar. Have we talked?

TheWitness

doublek · Post by **doublek** » Fri Apr 07, 2006 10:08 am

Not yet but I was hoping I could bounce a few ideas off of you and see what some of our limitations might be.

Were currently looking into splitting the rrdtool updates out of the poller.php script and just dumping the updates over to another MySQL table and running multiple rrdtools in the background to keep up with the requests.

Post by **rony** » Fri Apr 07, 2006 10:19 am

I sent you an email, please respond..

doublek · Post by **doublek** » Fri Apr 07, 2006 10:29 am

Sorry about that. To many late nights and not enough time to check all my e-mail. I just sent off the reply.

cactiuser0 · Post by **cactiuser0** » Fri Apr 07, 2006 11:23 am

Need to learn the experience from mrtg.

jrobey · Post by **jrobey** » Fri Apr 07, 2006 3:47 pm

Update: Alright, at this point, we have had to pull our data locally since our NAS is having issues. Things are extremely slow to local disk, so I hope to get our data back on the NAS shortly.

In trying to build the latest cactid from repository (to get around the timeout issue) I get a compile error at or around line 161 before { results included below. Commenting out the conditional branch starting at line 600 takes care of the issue so I can test, but may not be the best thing to do

Anything look wrong w/ my command or is there a typo here that I'm not seeing?

make results:
if gcc -DHAVE_CONFIG_H -I. -I. -I./config -I/usr/local/include/net-snmp -I/usr/local/include/net-snmp/.. -I/usr/local/include/mysql -g -O2 -MT util.o -MD -MP -MF ".deps/util.Tpo" -c -o util.o util.c; then mv -f ".deps/util.Tpo" ".deps/util.Po"; else rm -f ".deps/util.Tpo"; exit 1; fi
util.c: In function `cacti_log':
util.c:601: error: syntax error before '{' token
util.c: At top level:
util.c:609: error: syntax error before "return"
*** Error code 1

Stop in /usr/home/jrobey/cactid.
(3 of

: error: syntax error before '{' token

jrobey · Post by **jrobey** » Fri Apr 07, 2006 3:55 pm

Guess I've been looking to hard. Looks like the closing paren in second condition was missing. Still on the hunt for speed. Testing this then splitting off the rrdtool update from poller.php.

jrobey · Post by **jrobey** » Fri Apr 07, 2006 3:58 pm

/branches/BRANCH_0_8_6/cactid/util.c

looks like that error was put in during the last commit.

Post by **TheWitness** » Sat Apr 08, 2006 5:54 am

Can you please publish a bug report at http://bugs.cacti.net

Thanks,

TheWitness

Cacti

Cacti Limitations

Cacti Limitations

Mem / CPU

Still going

Found it

Forgot to post the branch I was working in

Who is online