[rt-users] RT 4 Upgrade Slow Performance - CustomFields?

Nathan Baker bakern at gmail.com
Sun Jun 3 00:00:40 EDT 2012


I agree with your recommendation in general for most installations,
especially ones larger than ours.  I don't think increasing the
KeepAliveTimeout is necessary anymore now that I fixed the swapping issue,
because the initial page load does not take a long time anymore.  However,
for our environment I know that there will never be more than 5 people
accessing the site at once, so we will never run into the scenario you were
giving as an example.  The reason I left the KeepAliveTimeout at 60 was
because I'd like to have it as fast as possible once a user starts doing
something, and I think a user could look at a ticket for more than 15
seconds (the default KeepAliveTimeout in my apache configuration) and then
continue on, but it's not as likely they would take longer than 60 seconds
in between clicks.  For our environment it would be fine to have 5 apache
processes dedicated for 5 users at once.

Thanks for the information on the lightweight front-end, it looks like it
would help a lot, although I think it might be overkill for our relatively
small installation.


On Sat, Jun 2, 2012 at 6:00 PM, Ruslan Zakirov <ruz at bestpractical.com>wrote:

> It shouldn't be necessary if you know how to fit things in.
> You don't want KeepAliveTimeout to be very high. Keep alive at 60
> seconds means that user when touched apache process holds it from
> serving other users for 60 seconds even if he doesn't do anything. 10
> users hit the server within a minute - you need 11 apache processes to
> serve next user. Your deployment is not configured for such values.
> For big keep alive values you need two step processing with light
> frontend and heavy backend. Frontend keep connections open and can
> hold many of them with low footprint. For example take a look at the
> following blog post:
> http://blog.webfaction.com/a-little-holiday-present, especially memory
> footprint chart.
> As the backend you either use FCGI server running RT, your current
> apache setup or something else.
> Take a look at the following extension:
> http://search.cpan.org/~ruz/RT-Extension-Nginx-0.02/lib/RT/Extension/Nginx.pm#FEATURES
> It generates config for nginx where a few features of the server and
> knowledge of RT are used to lower memory footprint, increase
> concurrency, lower page load times.
> --
> Best regards, Ruslan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20120603/0d0b92f0/attachment.htm>

More information about the rt-users mailing list