Webserver

Pre-established database connections
Preloaded modules - startup.pl
Reload Perl modules when updated on disk
Choosing the Right Strategy
mod_gzip/mod_deflate

Of course you should use mod_perl 2.0 ( http://perl.apache.org/ ). It's much faster (~ *100) than pure CGI, but it needs more RAM.

Pre-established database connections

You can have the database connections pre-established on startup of the web server. This saves time (see README.webserver).

Preloaded modules - startup.pl

Use the startup script scripts/apache2-perl-startup.pl for preloaded/precompiled Perl modules on your mod_perl webserver to be faster, with a smaller memory footprint (see README.webserver).

Reload Perl modules when updated on disk

By default Apache::Reload is used in scripts/apache2-httpd.include.conf. Disable it and you will get 8% more speed. But remember to restart the web server if you install any modules via the OTRS Package Manager, or any values in your SysConfig or in Kernel/Config.pm.

Important

This would also mean you can't use the OTRS Package Manager via the web interface, you will need to use the console commands: bin/otrs.Console.pl Admin::Package::*.

Choosing the Right Strategy

If you have a larger installation, e.g. over 1,000 new tickets per day and over 40 agents, it is a good idea to read the chapters on Performance of the mod_perl User's Guide ( http://perl.apache.org/docs/2.0/user/index.html ).

mod_gzip/mod_deflate

If your bandwidth is small, use mod_deflate for Apache2. If you have an html page with 45k, mod_gzip/mod_deflate compresses it to about 7k. The drawback is that this increases the load on the server side.