I have upgraded RT2 to 1.3.72 and DBIx-SearchBuilder-0.31. I found that
shorter queues loads ok, but larger queues( with lots of tickets) stil takes
quite long to load. Since we mostly work on those new and open tickets most
of the time, I am thinking if we split up the Tickets table into several
tables according to the status. Say, one table for resolved, another for
dead, etc.
Nobel
Heya Nobel,
There’s a known issue with SearchBuilder 0.31 and RT 1.3.72 that
will definitely cause it to grind with large amounts of data.
Just so we know, what OS / Database combo are you using (including
versions) and what's your hardware config like? Also, how
many tickets is 'lots of tickets'?
thanks,
jesseOn Tue, May 15, 2001 at 05:46:18PM +0800, Nobel Tse wrote:
I have upgraded RT2 to 1.3.72 and DBIx-SearchBuilder-0.31. I found that
shorter queues loads ok, but larger queues( with lots of tickets) stil takes
quite long to load. Since we mostly work on those new and open tickets most
of the time, I am thinking if we split up the Tickets table into several
tables according to the status. Say, one table for resolved, another for
dead, etc.Nobel
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent – root@eruditorum.org – jesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
pretty soon we’re going to HAVE to have hypertext mail!
–Tim Berners Lee. (8 Jan 1993 on www-talk)