Add docs to achieve 200K scale. #7812
Conversation
|
Newest code from mattermost has been published to preview environment for Git SHA b570ce6 |
agnivade
added
1: Dev Review
|
|
||
| .. note:: | ||
| - Usage of CPU, RAM, and storage space can vary significantly based on user behavior. These hardware recommendations are based on traditional deployments and may grow or shrink depending on how active your users are. | ||
| - From Mattermost v10.4, Mattermost Enterprise customers can configure `Redis <https://redis.io/>`_ (Remote Dictionary Server) as an alternative cache backend. Using Redis can help ensure that Mattermost remains performant and efficient, even under heavy usage. See the :ref:`Redis cache backend <configure/environment-configuration-settings:redis cache backend>` configuration settings documentation for details. |
There was a problem hiding this comment.
Do we need the Remote Dictionary Server parenthesis?
| - From Mattermost v10.4, Mattermost Enterprise customers can configure `Redis <https://redis.io/>`_ (Remote Dictionary Server) as an alternative cache backend. Using Redis can help ensure that Mattermost remains performant and efficient, even under heavy usage. See the :ref:`Redis cache backend <configure/environment-configuration-settings:redis cache backend>` configuration settings documentation for details. | |
| - From Mattermost v10.4, Mattermost Enterprise customers can configure `Redis <https://redis.io/>`_ as an alternative cache backend. Using Redis can help ensure that Mattermost remains performant and efficient, even under heavy usage. See the :ref:`Redis cache backend <configure/environment-configuration-settings:redis cache backend>` configuration settings documentation for details. |
There was a problem hiding this comment.
I don't know, this was already there. Will defer to Carrie.
| Example | ||
| ~~~~~~~ | ||
|
|
||
| A 100000-person team with medium usage (with a safety factor of 2x) would require between 10.56TB :sup:`1` and 52.8TB :sup:`2` of free space per annum. | ||
|
|
||
| :sup:`1` 100000 users * 5 MB * 12 months * 2x safety factor | ||
|
|
||
| :sup:`2` 100000 users * 25 MB * 12 months * 2x safety factor | ||
|
|
||
| We strongly recommend that you review storage utilization at least quarterly to ensure adequate free space is available. |
There was a problem hiding this comment.
Should this example be updated to 200k?
There was a problem hiding this comment.
Yes please: the 100K inline references and the final calculation of free space
cwarnermm
added
Awaiting Submitter Action
| .. include:: ../_static/badges/ent-selfhosted.rst | ||
| :start-after: :nosearch: | ||
|
|
||
| This page describes the Mattermost reference architecture designed for the load of up to 200000 concurrent users. Unsure which reference architecture to use? See the :doc:`scaling for enterprise </scale/scaling-for-enterprise>` documentation for details. |
There was a problem hiding this comment.
Do we want to add here that 200k concurrent users translates to approximately 500k supported users, depending on expected usage?
There was a problem hiding this comment.
IMO we should retire that heuristic. The ratio of concurrent:total varies highly from customer to customer. It is clearer to simply focus on concurrent users.
|
Newest code from mattermost has been published to preview environment for Git SHA 354fc32 |
|
/update-branch |
|
Newest code from mattermost has been published to preview environment for Git SHA c834532 |
No description provided.