RT 2.0.12 + postgres

Hi everyone,

We’re using rt with postgres here.
Since i updated RT 2.0.7 to 2.0.12 people are complaining that RT is very
slow.
The first page and the search page is normal. But display a ticket and
update an tickets pages
are realy slow.

On the system we see that postgres is eating all the resources.
Anybody know how it’s possible that rt became so slow ?

Because it’s so slow, we’re considering the following:

  • Delete all tickets with status dead (most spam)
  • Archiving old tickets on another rt instance
  • investigate mysql speed

Anybody done this before or has other hints for me ?

Regards,

Bas Toonk
Medewerker beheer

ZXFactory - Solutions for streaming media, unified messaging and internet
services.

ZXFactory BV
Telefoonweg 44b
6712 GD Ede
The Netherlands
T +31 318 693 111
F +31 318 693 042
E B.Toonk@zx.nl
I www.zx.nl

“BT” == Bas Toonk B.Toonk@zx.nl writes:

BT> Since i updated RT 2.0.7 to 2.0.12 people are complaining that RT is very
BT> slow.
BT> The first page and the search page is normal. But display a ticket and
BT> update an tickets pages
BT> are realy slow.

Compare the database schemas from what you have to what comes with
2.0.12 and add the missing indices. Also, make sure you “VACUUM
ANALYZE” your rt database every so often, to keep Postgres’ statistics
accurate. I do this nightly.

Make sure your Perl module dependencies are up-to-date.

Postgres works great with RT.