Performance improvements when retrieving a ticket

RT Users
1

Hi All,

We’re at rt v2.0.9. We have about 4000 tickets in our system.

Since this release, have there been any performance improvements when
getting tickets? Tickets that have say 10 - 20 transactions or comments
take a long time to retrieve on our system, and I noticed there are many
queries for each comment/transaction.

Anyone know if this has been optimized in any of the later versions of rt?

Also - anyone have any tips on optimizing the DB?

We vacuum it nightly, and it does seem all the fields he queries on are
indexed already.

We’re using postgresql - is this operation significantly faster with mysql?

Thanks
Nick
Nicolae P. Costescu, Ph.D. / Senior Developer
Stronghold Technologies
46040 Center Oak Plaza, Suite 160 / Sterling, Va 20166
Tel: 571-434-1472 / Fax: 571-434-1478

2

“NPC” == Nicolae P Costescu nick@strongholdtech.com writes:

NPC> We vacuum it nightly, and it does seem all the fields he queries on are
NPC> indexed already.

Do you vacuum analyze or just vacuum?

Have you ever run a “vaccum full” to clear out old data?

Did you tune postgres from the defaults? The defaults are pretty
damned lame for anything but toy DBs.

Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/

3

“NPC” == Nicolae P Costescu nick@strongholdtech.com writes:

NPC> We vacuum it nightly, and it does seem all the fields he queries on are
NPC> indexed already.

One more thing to try after a vacuum full is to reindex all the
indices. At the psql prompt when connected to the rt2 database, type
“\di” to list them, then run “reindex index XXX” for each one listed.

When you have a lot of churn in your database the indexes tend to
grow. This is being worked on for the next release of PG, I hear.