[rt-users] Proper Server for RT

[Mat]

> Can you comment on what tuning you've done to improve your
> performance?  Is it mainly indexing tables?  Does RT set up table
> indexes?  If not, perhaps it should (I keep meaning to look at this,
> but always get sidetracked before I get to it).

Main tuning is just making sure mysql has enough memory avaliable so that it
is not
swapping out large sort tables onto disk.
I found that when rt needs to resolve a requestor using the watchers table
that
it does not touch the indexes in place, i've also tried in vain to try
and create an index that gets used (even went to the mysql mailing list),
but
still, this query looks at every single row, creating a major bottle neck. I
believe the way the watchers table is set up that its not possible to
get mysql to use an index on it (I could be wrong, would have to go
back and have alook at the mysql docs)

> Perhaps you'd also care to comment on how the design of the database
> might be improved, so that future releases can be improved (if someone
> decides to look into it...)?

I believe jeese has totally redesigned how watchers (and therefor
requestors) work
with the latest development release of rt. Also he is using innodb tables
which
should make things much happier (as large queries shouldn't lock the entire
table, stopping everything behind them). Basically some schema that is
able to have an index against it will be good, but I ain't no dba,so what
exactly the best one would be has me stumped :)

Mat Watson
Netspace online systems.


>
> --
> Derek Martin
> Lead Network Engineer
> ddm at skillsoft.com
> (603)324-3000 x516