Memory problem when searching

RT Users
1

When doing searches for relatively large batches of tickets (+/- 5000
tickets) my machine just grinds to a halt. If I do the same search on RT1
on the same dataset, there is no problem.

At first I thought it was lack of resources, but I have upgraded to a 1G
256M machine, and still it stalls. Is RT2 so much more memory intensive, or
am I misconfigured? It happens especially on the searches.

Apache, Perl, mod_perl are all installed with rpms (RH 7.1), so I am not
sure if mod_perl is installed as a DSO, or if this could at all be the
problem as noted in the documentation.

Any suggestions on how I can configure Apache/WebRT to work better?

Rehan van der Merwe

2

Try limiting the resultset to 10/25/50/100 tickets per page.On Wed, Aug 01, 2001 at 05:10:58PM +0200, Rehan van der Merwe wrote:

When doing searches for relatively large batches of tickets (+/- 5000
tickets) my machine just grinds to a halt. If I do the same search on RT1
on the same dataset, there is no problem.

At first I thought it was lack of resources, but I have upgraded to a 1G
256M machine, and still it stalls. Is RT2 so much more memory intensive, or
am I misconfigured? It happens especially on the searches.

Apache, Perl, mod_perl are all installed with rpms (RH 7.1), so I am not
sure if mod_perl is installed as a DSO, or if this could at all be the
problem as noted in the documentation.

Any suggestions on how I can configure Apache/WebRT to work better?

Rehan van der Merwe

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – root@eruditorum.org – jesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

This is scary. I’m imagining tracerouting you and seeing links like “Route
84” and “Route 9, Exit 14”. Obviously, this is illness induced.
–Cana McCoy