Cheshire Cat Computing

Various things can improve the speed of the routers2.cgi frontend. By far the most effective for UNIX people is to install speedycgi, make sure you have Perl 5.8, and make the my/our changes shown at the beginning of the script. This can make a tenfold performance improvement.

Other things to try:

1) remove all comments from the routers2.conf and the .cfg files
2) make sure you dont have too many targets in each .cfg file
3) make sure your .rrd and .cfg files, and graphpath, are on striped disks, with fast access times. Put graphpath and the .rrd files on different filesystems.
4) don't use 'extendedtime = test'. Either have yes or no.
5) dont use 95th percentile calculations.

Steve

version 2.14beta6 has experimental code for caching support using speedycgi and mod_perl. This makes the various threads cache the .cfg file contents (with the appropriate caveats for changing these files without restarting the threads).

Initial trials of this have been extremely promising -- works fine here, and a beta site has reported response times falling from up to 15s down to <1 sec (after initial caching run).

So far, tested with speedycgi (UNIX) and mod_perl (UNIX).

This code will be disabled by default, but may be a solution to sites with large numbers of big config files.

Anyone wanting to test 2.14beta6, please let me know via email.