Ever since upgrading to the 3.x series, I’ve had very slow performance
on the web interface for RT. Maybe I don’t notice this on the email
interface because it only makes small transactions instead of trying to
view the 17 comments in the ticket’s history. So, for all I know I’m
barking up the wrong tree.
I do know that performance is so bad that certain very long tickets do
not even load after 15 minutes.
DBIx::SearchBuilder version 1.15 and 1.16 have been tried with the same
Almost 5000 tickets
7 users that login
email interface available over postfix 2.0
I've tried to install RT 3.2.2 on a different server (athena) and
reference the DB storage on the first server (zeus). Watching “top” on
both of these servers shows the mysqld process on zeus to be barely
used at all while an httpd process on athena consumes all available CPU
time for well over a half hour (and still going, so I don’t know how
long it will take) and a lot of memory (151MB and still climbing).
This ticket displayed fine in RT version 2.0.15.
The migration from 2.0.15 to 3.2.2 involved an upgrade to 3.0, use of
the migration tools, and then another upgrade to 3.2. Since this
effects the DB storage and not the web GUI, I’m not sure if this is
relevant. The use of the FreeBSD ports collections was attempted, but
manual installation from source was found to work better. Its been a
few months since I’ve done this, so please forgive me for forgetting
how it worked better. I think that it just didn’t vs. did work, but
I am not completely certain.
The command line interface appears to want a password but none that I
try work. My shell username is the same as my RT username, but that
password and the DB user password do not work. I’m not sure if this is
Are there any tips that anyone can offer? Thanks in advance, Jaime
Cairo-Durham Central School District