Zammad for 1000 agents

Technical assistance
1

Infos:

  • Used Zammad version: 6.0
  • Used Zammad installation type: (source, package, docker-compose, …) packge using apt
  • Operating system: ubuntu22.04
  • Browser + version: any

Expected behavior:

  • Zammad should work with 1000 agents

Actual behavior:

  • Zammad not working when there are 1000 agents

Steps to reproduce the behavior:

  • run zammad with 1000 agents
2

Question out of curiosity, what does your server infrastructure look like?

3

And what means 1000 agents? Concurrent agent sessions at the same time?

4

Zammad 6.0 is outdated. We’re at Zammad 6.2 which is a security release.

Instructions unclear. Please provide tuning settings if applicable. And note that it’s about concurrent agents not the total agents you have in your system.

Also tell us “What does not work” that would help a lot.

1 Like
5

Sorry My bad, We are using version 6.2

6

zammad config:get WEB_CONCURRENCY =50
zammad config:get ZAMMAD_SESSION_JOBS_CONCURRENT = set
zammad config:get ZAMMAD_PROCESS_SCHEDULED_JOBS_WORKERS = 1
zammad config:get ZAMMAD_PROCESS_DELAYED_JOBS_WORKERS =4

Machine size GCP c3 std with 44 CPU and 176 GB Memory 128 gb standard pd DIsk

Following issue-

Frequent upstream error
DIsk getting full for no reason automatically it comes to normal size
Email Fetching issue with following errors-

  • Channel: Google::Account in is active but not fetched for about 8 hours
  • unprocessable mails: 103
  • scheduler may not run (last execution of CacheClearJob.perform_now 10 days ago) - please contact your system administrator

Search related issues -Search doesnt happen sometime- We have to reindex then it starts working.

7

Concurrent agent is between 300 to 500

Thanks for reply.

8

Machine size GCP c3 std with 44 CPU and 176 GB Memory 128 gb standard pd DIsk

9

Updated details:

Zammad version 6.2

Infra:
Machine size GCP c3 std with 44 CPU and 176 GB Memory 128 gb standard pd DIsk

Tunning:
zammad config:get WEB_CONCURRENCY =50
zammad config:get ZAMMAD_SESSION_JOBS_CONCURRENT = set
zammad config:get ZAMMAD_PROCESS_SCHEDULED_JOBS_WORKERS = 1
zammad config:get ZAMMAD_PROCESS_DELAYED_JOBS_WORKERS =4

Following issues-

Frequent upstream error
DIsk getting full for no reason automatically it comes to normal size
Email Fetching issue with following errors-

  • Channel: Google::Account in is active but not fetched for about 8 hours
  • unprocessable mails: 103
  • scheduler may not run (last execution of CacheClearJob.perform_now 10 days ago) - please contact your system administrator

Search related issues -Search doesnt happen sometime- We have to reindex then it starts working.

10

You’re setting up Zammad for up to 1000 (!) agents on cloud hardware that costs no less than $15k per year, and yet you have not considered getting commercial support from Zammad directly?

3 Likes