RT 3.2 Performance problem

Hi All,

When more than one person accesses RT at the same time
only one persons request appears to happen at any time.

For example, in Mozilla I open two tabs to RT. In one
tab I do a bulk update of 1000 tickets which takes
some time. In the other tab I then request the RT
main page. The second request is not served until
the bulk update is done.

From httpd.conf:

MinSpareServers 5
MaxSpareServers 10
StartServers 5

When only one request happens at a time the performance
is fine.

Suggestions?

Thanks!

-Todd

Hi All,

When more than one person accesses RT at the same time
only one persons request appears to happen at any time.

For example, in Mozilla I open two tabs to RT. In one
tab I do a bulk update of 1000 tickets which takes
some time. In the other tab I then request the RT
main page. The second request is not served until
the bulk update is done.

Right. because RT does session locking. when you’re using the same
browser, you use the same session cookie.
If you were using another browser (not another tab or window), you
wouldn’t see the same thing. Of course, hammering the database with
1000 ticket updates is also going to slow performance.