We are running RT 3.8.1, Apache 2.2.3 with mysql 5.0.45 on a separate
machine over (at least) 100bT connections.
The web interface to RT3 seems slow to me (I want computers to react
faster than I can, i.e. preferably under 300ms). From clicking on a
ticket in “found N tickets” to seeing the full ticket information can
take up to 7 seconds, even with only 4 or so fairly short attachments.
(the Firefox client is reasonably unloaded and displays other websites
fairly quickly, generally under a second for ones on the LAN).
Our system is not especially busy - not serving lots of concurrent users.
Usually only 1 I suspect.
I have been through some of the tuning guides (mysqltuner.pl,
PerformanceTuning - Request Tracker Wiki,
www.masonhq.com/docs/manual/Params.html) and tweaked some things to
DBIx::SearchBuilder.pm is version 1.54
/opt/rt3/etc/RT_SiteConfig.pm has e.g.
Set($LogToSyslog , ‘info’);
Set($LogToScreen , ‘error’);
Set($LogToFile , undef);
Interrogating the DB over the network seems reasonably fast:
$ time ( echo ‘use rt3 ; select * from Attachments where id = 20367 ; \q’ |
mysql -h rt3db -pXXX )
Using the command-line client over HTTP/SSL is somewhat slower, but still
$ time rt show ticket/2143/attachments
Any suggestions / stupid stuff to check ?
Andrew Daviel, TRIUMF, Canada
Tel. +1 (604) 222-7376 (Pacific Time)
Network Security Manager