<commit_before>Hardware
********

You can run Zammad on bare metal or on a virtual machine. Choose what you prefer.

For Zammad and a database server like PostgreSQL we recommend at least:
=======================================================================

* 2 CPU cores
* 4 GB of RAM (+4 GB if you want to run Elasticsearch on the same server)

For optimal performance up to 40 agents:
========================================

* 4 CPU cores
* 6 GB of RAM (+6 GB if you want to run Elasticsearch on the same server)

Of course at the end it depends on acutal load of concurent agents and data traffic.

.. note:: We can't suggest any disk space recommendations, as this highly depends on how you work. Zammad will always try to recognize the same attachments and store it just once.

Performance Tuning
==================

As the number of active users on your system grows,
performance will eventually degrade, leading to:

   * delays for outgoing email,
   * long loading times when viewing or creating tickets,
   * stale or out-of-sync search results, or
   * stale or out-of-sync ticket overviews.

You may see modest improvements by
:ref:`setting certain environment variables for Performance Tuning <performance_tuning>`,
such as ``$WEB_CONCURRENCY`` or ``$ZAMMAD_SESSION_JOBS_CONCURRENT``.<commit_msg>Maintenance: Fix line lengths of hardware.rst<commit_after>Hardware
********

You can run Zammad on bare metal or on a virtual machine. Choose what 
you prefer.

For Zammad and a database server like PostgreSQL we recommend at least:
=======================================================================

* 2 CPU cores
* 4 GB of RAM (+4 GB if you want to run Elasticsearch on the same server)

For optimal performance up to 40 agents:
========================================

* 4 CPU cores
* 6 GB of RAM (+6 GB if you want to run Elasticsearch on the same server)

Of course at the end it depends on acutal load of concurent agents and 
data traffic.

.. note:: 

   We can't suggest any disk space recommendations, as this highly depends on 
   how you work. Zammad will always try to recognize the same attachments and 
   store it just once.

Performance Tuning
==================

As the number of active users on your system grows,
performance will eventually degrade, leading to:

   * delays for outgoing email,
   * long loading times when viewing or creating tickets,
   * stale or out-of-sync search results, or
   * stale or out-of-sync ticket overviews.

You may see modest improvements by
:ref:`setting certain environment variables for Performance Tuning <performance_tuning>`,
such as ``$WEB_CONCURRENCY`` or ``$ZAMMAD_SESSION_JOBS_CONCURRENT``.
{'fraction_non_alphanumeric': 0.14706980216498694, 'fraction_numerical': 0.0059723777528928705, 'mean_word_length': 4.606694560669456, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4302374', 'n_tokens_mistral': 717, 'n_tokens_neox': 658, 'n_words': 364}