Performance Tuning

There is a list of performance enhancing techniques for your OTRS installation, including configuration, coding, memory use, and more.

Ticket Search Index

OTRS uses a special search index to perform full-text searches across fields in articles from different communication channels.

To create an initial index, use this command:

otrs> /opt/otrs/bin/ Maint::Ticket::FulltextIndex --rebuild


Actual article indexing happens via an OTRS daemon job in the background. While articles which were just added in the system are marked for indexing immediately, it could happen their index is available within a few minutes.

There are some options available for fine tuning the search index:


Basic full-text index settings.

``Ticket::SearchIndex::Attribute`` Setting

Ticket::SearchIndex::Attribute Setting


Run the following command in order to generate a new index:

otrs> /opt/otrs/bin/ Maint::Ticket::FulltextIndexRebuild
Defines the maximum number of words which will be processed to build up the index. For example only the first 1000 words of an article body are stored in the article search index.
WordLengthMin and WordLengthMax
Used as word length boundaries. Only words with a length between these two values are stored in the article search index.

Full-text index regular expression filters to remove parts of the text.

``Ticket::SearchIndex::Filters`` Setting

Ticket::SearchIndex::Filters Setting

There are three default filters defined:

  • The first filter strips out special chars like: , & < > ? ” ! * | ; [ ] ( ) + $ ^ =
  • The second filter strips out words which begin or ends with one of following chars: ‘ : .
  • The third filter strips out words which do not contain a word-character: a-z, A-Z, 0-9, _

English stop words for full-text index. These words will be removed from the search index.

``Ticket::SearchIndex::StopWords###en`` Setting

Ticket::SearchIndex::StopWords###en Setting

There are so-called stop-words defined for some languages. These stop-words will be skipped while creating the search index.

See also

If your language is not in the system configuration settings or you want to add more words, you can add them to this setting:

  • Ticket::SearchIndex::StopWords###Custom

Article Storage

There are three different back end modules for the article storage of phone, email and internal articles. The used article storage can be configured in the setting Ticket::Article::Backend::MIMEBase::ArticleStorage.


This default module will store attachments in the database. It also works with multiple front end servers, but requires much storage space in the database.


Don’t use this with large setups.


Use this module to store attachments on the local file system. It is fast, but if you have multiple front end servers, you must make sure the file system is shared between the servers. Place it on an NFS share or preferably a SAN or similar solution.


Recommended for large setups.


Use this module to store attachments in any AWS S3 compatible object storage.


This module is currently only usable by adding the following code snippet to Kernel/ manually.

$Self->{'Ticket::Article::Backend::MIMEBase::ArticleStorage'} = 'Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageObjectFS';

$Self->{'Ticket::Article::Backend::MIMEBase::ArticleStorageObjectFS'} = {
    Endpoint      => '',   # HTTP requests base endpoint, optional.
    Region        => 'local',                   # The region that service objects will be instantiated with.
    AwsAccessKey  => 'minioadmin',              # A "login" which grants programmatic access to your resources.
    AwsSecretKey  => 'minioadmin',              # A "secret" which grants programmatic access to your resources.
    Bucket        => 'storage',                 # The logical container of objects
    HealthCheck   => '/minio/health/live',      # A (relative) URL path for a service health / alive check, optional.
    MaxObjectSize => 1024 * 1024 * 20,          # A value in bytes to limit the size of a single object, optional, default 100 MiB.

You can switch from one back end to the other on the fly. You can switch the back end in the system configuration, and then run this command line utility to put the articles from the database onto the file system or the other way around:

otrs> /opt/otrs/bin/ Admin::Article::StorageSwitch --target ArticleStorageFS

You can use the --target option to specify the target back end.


The entire process can take considerable time to run, depending on the number of articles you have and the available CPU power and/or network capacity.

If you want to keep old attachments in the database, you can activate the system configuration option Ticket::Article::Backend::MIMEBase::CheckAllStorageBackends to make sure OTRS will still find them.

Archiving Tickets

As OTRS can be used as an audit-proof system, deleting closed tickets may not be a good idea. Therefore we implemented a feature that allows you to archive tickets.

Tickets that match certain criteria can be marked as archived. These tickets are not accessed if you do a regular ticket search or run a generic agent job. The system itself does not have to deal with a huge amount of tickets any longer as only the latest tickets are taken into consideration when using OTRS. This can result in a huge performance gain on large systems.

To use the archive feature:

  1. Activate the Ticket::ArchiveSystem setting in the system configuration.

  2. Define a generic agent job:

    • Click on the Add Job button in the Generic Agent screen.
    • Job Settings: provide a name for the archiving job.
    • Automatic Execution: select proper options to schedule this job.
    • Select Tickets: it might be a good idea to only archive those tickets in a closed state that have been closed a few months before.
    • Update/Add Ticket Attributes: set the field Archive selected tickets to archive tickets.
    • Save the job at the end of the page.
    • Click on the Run this task link in the overview table to see the affected tickets.
    • Click on the Run Job button.


    Up to 5000 tickets can be modified by running this job manually.

When you search for tickets, the system default is to search tickets which are not archived.

To search for archived tickets:

  1. Open the ticket search screen.
  2. Set Archive search to Unarchived tickets or All tickets.
  3. Perform the search.

Tuning the Web Server

The built-in web server of OTRS can handle small and medium setups out of the box. When OTRS serves many users simultaneously, it may be necessary to tweak the web server configuration to increase the number of worker processes, for example.

The web server configuration file is located in Kernel/WebApp.conf, and all settings there are documented. The worker setting can be increased to deploy more processes for serving HTTP requests on capable servers.


OTRS caches a lot of temporary data in /opt/otrs/var/tmp. Please make sure that this uses a high performance file system and storage. If you have enough RAM, you can also try to put this directory on a ramdisk like this:

otrs> /opt/otrs/bin/ Maint::Session::DeleteAll
otrs> /opt/otrs/bin/ Maint::Cache::Delete
root> mount -o size=16G -t tmpfs none /opt/otrs/var/tmp


Add persistent mount point in /etc/fstab.


This will be a non-permanent storage that will be lost on server reboot. All your sessions (if you store them in the file system) and your cache data will be lost.


For very high loads, it can be required to operate OTRS on a cluster of multiple front end servers. This is a complex task with many pitfalls. Therefore, OTRS Group provides support for clusters in its managed OTRS environment exclusively.

Limits of Objects

There is no technical limitation of how many objects can be used in the system but using high number of objects may affect the system performance. The proposed limits apply only to objects that are set as valid. The objects set as invalid or invalid-temporarily are not used by the system.

To keep the system fast and responsive the following limits for valid objects should not be exceeded:

  • Mail accounts: 10
  • Postmaster filters: 50
  • ACLs: 80
  • Dynamic fields: 300
  • Dynamic field dropdown or multiselect values per field: 100
  • Services: 500
  • SLAs: 50
  • Queues: 200
  • Configuration item classes: 20
  • Configuration item objects: 20,000
  • Processes: 50
  • Generic agents: 30 (frequency max once per hour per generic agent)
  • Ticket states: 20
  • Ticket types: 10
  • Appointment calendars: 50
  • Articles per ticket: 500