This sounds like you have some agents and customers using Zammads UI. No problem, but it will need tuning.
You can learn more in the documentation
or… if you prefer video content, I am explaining that stuff in this video.
I’ve watched your YouTube video with very high interest! Thank you so much for pointing it out to me!
As this is a rather new deployment with few active users and very little data, the key performance tips that I got from the video were:
- raising the DB connections in postgres from 50 to about 2000
- Increasing ElasticSearch’s RAM Budget
To the postgres connections: The Zammad documentation mentions that the default value of 50 is plenty for most cases. (Can’t post link, it’s under Configure Database Server, the top paragraph)
Maybe ElasticSearch is slowing down the system, but I’d like to find some sort of confirmation in the log files before I start twiddling with parameters.
Do you (or anyone else, of course!) have any further pointers (maybe a specific log file/entry?) where I can see the cause of the slow railsserver reponses?
Sorry the forum software flagged your edit as spam and I got confused due their wording… Due to this anonymous users can no longer read your initial post (I can’t unhide it…).
I’ll try to remember that post at a later post, it’s marked as read on my account now so..
Original post was:
Infos:
- Used Zammad version: 6.5.2
- Used Zammad installation type: docker-compose
- Operating system: Ubuntu 24.04.3 LTS
- Browser + version: any
Expected behavior:
- Using the website is fast and reliable
Actual behavior:
- Occasionally, requests take a very long time to be fulfilled, sometimes failing entirely.
I’ve checked the logs using
docker compose logs zammad-railsserver and I see many 200 OK requests fulfilling in over 1000ms. Often the reported ActiveRecords time is quite high as well (maybe around 50% of the total time) and the GC-time is often between 100ms to 300ms.
Below you will find a couple example lines.
I’ve followed the docker-compose deployment guide (elastic search enabled): Install with Docker — Zammad System Documentation documentation
I’ve also followed the other guide to add an nginx reverse proxy for https: Docker Compose Scenarios — Zammad System Documentation documentation
The VM is a clean install and has 4 CPU cores with 8GB RAM. Htop is reporting 1-10% cpu usage, with 5GB/8GB used. There isn’t a lot of traffic with a maximum of 3-4 Users at any given time.
Are there any other pointers I could check? Maybe some other log files? Thank you very much!
zammad-railsserver-1 | I, [2026-02-25T16:37:43.154464#1-663540] INFO -- : Processing by TicketsController#show as JSON
zammad-railsserver-1 | I, [2026-02-25T16:37:43.198374#1-663540] INFO -- : Parameters: {"all"=>"true", "auto_assign"=>"true", "_"=>"1772014767751", "id"=>"39"}
zammad-railsserver-1 | I, [2026-02-25T16:37:43.155563#1-663700] INFO -- : Started GET "/api/v1/tickets/71?all=true&auto_assign=true&_=1772014767755" for 172.18.0.1 at 2026-02-25 16:37:43 +0100
zammad-railsserver-1 | I, [2026-02-25T16:37:43.192523#1-663660] INFO -- : Processing by TicketsController#show as JSON
zammad-railsserver-1 | I, [2026-02-25T16:37:43.236108#1-663660] INFO -- : Parameters: {"all"=>"true", "auto_assign"=>"true", "_"=>"1772014767754", "id"=>"70"}
zammad-railsserver-1 | I, [2026-02-25T16:37:43.202335#1-663720] INFO -- : Processing by TicketsController#show as JSON
zammad-railsserver-1 | I, [2026-02-25T16:37:43.245505#1-663720] INFO -- : Parameters: {"all"=>"true", "auto_assign"=>"true", "_"=>"1772014767756", "id"=>"74"}
zammad-railsserver-1 | I, [2026-02-25T16:37:43.252959#1-663400] INFO -- : Processing by TicketsController#show as JSON
zammad-railsserver-1 | I, [2026-02-25T16:37:43.253010#1-663400] INFO -- : Parameters: {"all"=>"true", "auto_assign"=>"true", "_"=>"1772014767749", "id"=>"33"}
zammad-railsserver-1 | I, [2026-02-25T16:37:43.279387#1-663560] INFO -- : Processing by TicketsController#show as JSON
zammad-railsserver-1 | I, [2026-02-25T16:37:43.279522#1-663560] INFO -- : Parameters: {"all"=>"true", "auto_assign"=>"true", "_"=>"1772014767753", "id"=>"45"}
zammad-railsserver-1 | I, [2026-02-25T16:37:43.376949#1-663620] INFO -- : Processing by TicketsController#show as JSON
zammad-railsserver-1 | I, [2026-02-25T16:37:43.377011#1-663620] INFO -- : Parameters: {"all"=>"true", "auto_assign"=>"true", "_"=>"1772014767752", "id"=>"37"}
zammad-railsserver-1 | I, [2026-02-25T16:37:43.449888#1-663700] INFO -- : Processing by TicketsController#show as JSON
zammad-railsserver-1 | I, [2026-02-25T16:37:43.449946#1-663700] INFO -- : Parameters: {"all"=>"true", "auto_assign"=>"true", "_"=>"1772014767755", "id"=>"71"}
zammad-railsserver-1 | I, [2026-02-25T16:37:43.979031#1-661720] INFO -- : Completed 200 OK in 1310ms (Views: 3.3ms | ActiveRecord: 796.3ms (72 queries, 16 cached) | GC: 275.2ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:44.413279#1-661800] INFO -- : Completed 200 OK in 1645ms (Views: 4.0ms | ActiveRecord: 810.4ms (79 queries, 19 cached) | GC: 290.3ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:44.755874#1-663180] INFO -- : Completed 200 OK in 1886ms (Views: 3.0ms | ActiveRecord: 898.7ms (77 queries, 20 cached) | GC: 300.0ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:44.765311#1-661940] INFO -- : Completed 200 OK in 1998ms (Views: 4.1ms | ActiveRecord: 756.7ms (87 queries, 22 cached) | GC: 300.0ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:44.879833#1-663300] INFO -- : Completed 200 OK in 1795ms (Views: 2.4ms | ActiveRecord: 884.0ms (71 queries, 16 cached) | GC: 285.6ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:44.886257#1-663220] INFO -- : Completed 200 OK in 1808ms (Views: 2.8ms | ActiveRecord: 890.1ms (76 queries, 20 cached) | GC: 285.8ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:44.959332#1-661760] INFO -- : Completed 200 OK in 2043ms (Views: 2.6ms | ActiveRecord: 982.6ms (81 queries, 21 cached) | GC: 293.6ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:44.990940#1-663360] INFO -- : Completed 200 OK in 1987ms (Views: 12.5ms | ActiveRecord: 929.5ms (82 queries, 20 cached) | GC: 298.7ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:45.002256#1-663540] INFO -- : Completed 200 OK in 1797ms (Views: 2.3ms | ActiveRecord: 1023.5ms (76 queries, 20 cached) | GC: 290.2ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:45.021967#1-661900] INFO -- : Completed 200 OK in 2086ms (Views: 6.8ms | ActiveRecord: 911.7ms (74 queries, 16 cached) | GC: 304.8ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:45.058444#1-663400] INFO -- : Completed 200 OK in 1805ms (Views: 3.0ms | ActiveRecord: 811.4ms (73 queries, 18 cached) | GC: 293.1ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:45.065672#1-663440] INFO -- : Completed 200 OK in 1978ms (Views: 5.6ms | ActiveRecord: 995.3ms (88 queries, 21 cached) | GC: 301.2ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:45.075600#1-663560] INFO -- : Completed 200 OK in 1796ms (Views: 3.8ms | ActiveRecord: 860.4ms (72 queries, 16 cached) | GC: 292.9ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:45.088996#1-663660] INFO -- : Completed 200 OK in 1853ms (Views: 4.1ms | ActiveRecord: 953.0ms (75 queries, 20 cached) | GC: 295.5ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:45.106726#1-663620] INFO -- : Completed 200 OK in 1729ms (Views: 2.5ms | ActiveRecord: 767.6ms (77 queries, 21 cached) | GC: 290.4ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:45.141699#1-663720] INFO -- : Completed 200 OK in 1896ms (Views: 3.0ms | ActiveRecord: 920.0ms (86 queries, 20 cached) | GC: 298.0ms)
zammad-railsserver-1 | I, [2026-02-25T16:37:45.144255#1-663700] INFO -- : Completed 200 OK in 1694ms (Views: 3.4ms | ActiveRecord: 920.3ms (82 queries, 17 cached) | GC: 290.0ms)