Zammad becomes slow / not usable

Infos:

  • Used Zammad version: 6.5.2-1758782245.b958e71f.bookworm
  • Used Zammad installation type: package
  • Operating system: Debian bookworm
  • Browser + version: Firefox latest, Chrome latest, egde latest
  • System: vmWare-VM, 4 cores on one socket, 32 GB RAM full reserved, 16 GB swap

Expected behavior:

  • qucik response when interact with web-gui

Actual behavior:

  • system slow / becomes not usable

Steps to reproduce the behavior:

  • restart machine

After restart the machine on ruby-process from user zammad runs permanent at 100%, another ruby process ist created. Round about 4 hours later system becomes unresponsive.

We have set up the db-connections to 2000 and increased the cache-values:
Configure Database Server — Zammad System Documentation documentation

The problem start 4 weeks ago with hundreds of notification messages inside one single ticket. so we deactivate the triggers.

Get’s slower over time definitely sounds like a database connection issue, because that’s basically the only thing that fills up over time in a relevant that is performance relevant. The config might be faulty and not apply the maximum connection setting correctly.

Additionally to that (because I’m lazy and performance tuning is a very broad and complex topic), this video might help you pinning down most of the issues on a normal level.

1 Like

Hi MrGeneration,

this video made my day. Now I’v understand the processes an dependencies from zammad. Now my system is stable and performant. Thank you for quick response an exellent help.

If you don’t know what to look for, it becomes difficult for people like me.

Best regards
cyrano330

2 Likes

Keep an eye on it some days. Performance issues love to come over time. Depending on their cause of course.

My main problem was the open changes and a ticket with 1200 notifications. Deleted – and the ruby ​​process is using 1% CPU. Thanks to your help, I now know where to look. Thanks again!

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