[rt-users] rt 2.09 / 2.0.13 performance (& SQL schema)

[Nate Amsden]

hi

i remember reading a while back(many moons ago ..) there was a newer ver
of RT that had an updated sql schema that was supposed to improve performance
i was wondering if I already had this schema in 2.09 or got it in my 2.13
upgrade today.  I did do /usr/local/rt/etc/insertdata 2.0.9 and it inserted
some new things into the db ...

but the performance seems the same as 2.0.9. for new tickets it is fast but
for older tickets it can get pretty slow.  I have 2 configurations:

Main production config:
RT 2.0.9
MySQL 3.23.40 compiled with many performance options
apache-ssl+mod_perl (DSO module)
P3-650 w/1GB ram, Ultra2 (80MB/s) SCSI drives
Debian woody (3.0)

soon to be production config(hopefully) 2 servers:
RT 2.0.13
apache-ssl+mod_perl (DSO module)
P3-450 w/512MB ram and Ultrawide (40MB/s) drive
Debian woody(3.0)

SQL server (already in production with several other DBs):
Dual P3-600 1GB Ram, Ultra2 (80MB/s) SCSI drives
MySQL 3.23.42 with many performance options as described in mysql docs
Debian Potato(2.2r5)

RT server is on the same 100mbit switched lan and connected to the SQL server.
the users of RT say the performance is about the same whether or not the DB
is local, so it doesn't appear that stunnel has any negative effects on it that
are noticable. I did see cpu usage spike for mysql when loading a real old
ticket on the SQL server(rt 2.0.13). my MySQL server is quite fast, this
particular server i have tested using another web-app called PureSecure
(formarlly DEMARC), and it made extensive use of mysql, my databases could
run 500+MB and it would still be fast, by contrast my rt2 db is 24MB(in
text-dumped format) and it's much slower ..my Puresecure systems at times
logged up to 40,000 network alerts per hour, and the server didn't even
hiccup.

any performance tips?

thanks for the great work on rt, its a real useful app, I'm glad i found it
when I did.

sofar i think we have about 800 tickets. though I haven't used rt much I just
see ticket id#s up to #809, not sure if older ones can be deleted ..

nate


-- 
Nate Amsden
System Administrator
GraphOn
http://www.graphon.com