[rt-users] Evil slow RT loading time

[Steve Poirier]

Hello,

There are some tips in the archive on how to optimize your db. We have over
20,000 tickets and load time is about 1 second with PIII-1000. Wait time was
about 4 seconds before optimization tips i saw on this list (primary
indexes). Also, we delete dead tickets, and backup and delete resolved
tickets older than 2 months, but they are still available on another system
just in case (very special case) someone would like to re-open a old ticket
instead of reopening a new one, two months after. This really help the
performance of our system. You can perform a search on fsck mailing lists
with htdig on indexes

Hope that help

Regards.
__
Steve Poirier
Directeur développement / Project Manager
Inet-Technologies inc.

----- Original Message -----
From: "J B Bell" <cipher at redback.com>
To: <rt-users at lists.fsck.com>
Sent: Saturday, September 29, 2001 9:57 PM
Subject: [rt-users] Evil slow RT loading time


> Well, I have finally gotten a conversion working from RT 1 to RT 2.  I
> went with mysql, because Pg died a horrible death at 4k tickets
> complaining of "out of memory!"  (Not sure which program threw this
> exception--the kernel, Pg, the import program, or what.)
>
> Unfortunately, the speed is even worse--MUCH worse--using an
> equivalent machine, the latest versions of mysql, apache, perl, and a
> perfectly black cat.  We're talking 4 to 5 minutes to load up a ticket
> from the list of owned ones.
>
> Our db is at over 29,000 tickets.  Does anyone have any optimization
> suggestions that have helped you in the past?  Is there a converter
> tool to go from RT2 mysql to RT2 Pg?  Should I have waited until
> Aldebaran was below the horizon?
>
> --JB
>
> _______________________________________________
> rt-users mailing list
> rt-users at lists.fsck.com
> http://lists.fsck.com/mailman/listinfo/rt-users
>