[rt-users] RT2 Speed/performance problems.

[Ayan R. Kayal]

Well, I think most of that stuff is to tune for ultimate speed. It's
probably not necessary, unless maybe you're running slower hardware,
which you're not. Most people probably don't tune to that extent, but I
could be wrong.

The Apache killing process thing though, that's a mod_perl thing.
Anything that uses mod_perl would probably have the same problem. It's
the only thing I've ever done to get acceptable speeds, which I would
qualify as definitely less than 3-10 seconds. It's worth trying, just to
see if it's a Quick Fix(tm), as it was for us. If not, sorry for wasting
your time.

As I said, when we first used tested RT, there was no speed problem.
After the first weekend/week when we basically filed 1000 tickets, all
the requests had bogged down mod_perl somewhat. In another week or two,
when it had bogged down more and everyone said wtf, I changed the number
of requests for Apache child processes. Problem gone...


Oh, and Dave, please chill out. :) 5 angry emails saying "you configured
it wrong" isn't too much more effective than 1 and tends to alienate
newbies.


The other ticketing system we tried was Keystone (after looking for even
a halfway decent one). Another department was using it unmodified for a
while, while my department only looked at the code in order to see if it
could be hacked to suit our purposes. Try modifying that beast. Some of
the ugliest PHP I have ever seen. And in terms of functionality, well,
it just didn't cut it... And is it even updated anymore?

O-                        ~ARK

> -----Original Message-----
> From: rt-users-admin at lists.fsck.com 
> [mailto:rt-users-admin at lists.fsck.com] On Behalf Of Maren S. Leizaola
> Sent: Tuesday, August 20, 2002 4:14 AM
> 
> Look at what you have above, you have to tune, mysql, mason, 
> the right version, make sure that mode perl does this, make 
> sure that apache kills the process after etc....