Performance optimization


  • Used Zammad version: 2.4
  • Used Zammad installation source: (source, package, …) deb
  • Operating system: Ubuntu 16.04
  • Browser + version: latest versions of: Chrome, Firefox, Edge (17)

Expected behavior:

  • Opening a ticket should take less than 3 seconds.

Actual behavior:

  • We use the latest version of zammad (2.4). Actually we are 15 agents with about 800 tickets. When we open a ticket we have to wait about 3 seconds to see it. The same if we want to edit an user or organisation. Our server is an VM with SSD Storage behind. It runs the lates ubuntu 16.04 LTS with 4 CPU and 8 GB of RAM as described in your documentation. The only thing we changed is, that we used apache2 as webserver not nginx.
    Is there any change to optimzie the installation. In the near feature we want to roll it out, than we have about 100 agents, but with this performance … we can’t.

We also run elasticsearch on the same machine. The database ist postgres 9.5

Hey @schmanat,

@martini helped out many people on here with the following recommendations.

1. RAMDisk
2. More application server processes.

Take a look at this

Hope this helps!


1 Like

Hey @svrn-dvnkln

thanks for your replay. I will have a look into your answer and hope it will help. I give feedback as soon as possible.

thanks again.


Hi everyone.

After setting the WEBCURRENCY to 4

zammad config:set WEB_CONCURRENCY=4
systemctl restart zammad

it seems it works faster. Thanks again for your hint.


What are the recommendations for the CPUs?

I want to set up a server that only runs Zammad. No other applications.
I plan to use:

  • 4 vCore
  • 8 GB Ram
  • 160 GB SSD

I can then choose between:

  • 4 processor, 1 core
  • 2 processor, 2 core
  • 1 processor, 4 core

What would you recommend?

Thanks a lot!


Hey @ecomsilio,

take a look at this, i think that’ll at least get you in the right direction :slight_smile:


1 processor with 4 cores should be fine

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.