From dfc3188cb78c34c66fe0c6d89e2cc182754949b5 Mon Sep 17 00:00:00 2001
From: Niels Lindenthal <n.lindenthal@openproject.com>
Date: Thu, 18 Jul 2024 10:12:30 +0000
Subject: [PATCH] Add sizing information for the project management module

---
 docs/requirements.md | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)

diff --git a/docs/requirements.md b/docs/requirements.md
index de9f74fe..7e4f580f 100644
--- a/docs/requirements.md
+++ b/docs/requirements.md
@@ -39,6 +39,44 @@ The following minimal requirements are thought for initial evaluation deployment
 | RAM  | 16 GB, recommended 32 GB                             |
 | Disk | HDD or SSD, >10 GB                                   |
 
+## Project management module
+
+For the project management module the following information can be used as a starting point for sizing decisions. 
+
+### Application server
+
+| Users | CPU cores | RAM   | web workers | background workers | disk space |
+| ----- | --------- | ----- | ----------- | ------------------ | ---------- |
+| <=200 | 4         | 4 GB  | 4           | 1                  | 20 GB      |
+| 500   | 8         | 8 GB  | 8           | 2                  | 40 GB      |
+| 1,500 | 16        | 16 GB | 16          | 4                  | 80 GB      |
+| 3,000 | 32        | 24 GB | 24          | 6                  | 160 GB     |
+
+Exact scaling requirements depend highly on the workload and number of concurrent users. Disk space scaling required only for logging and internal attachments (if any). Internal attachments are likely stored on object storage in the openDesk deployment.
+Majority of remaining disk space growth happens on the database.
+
+Please see the docs for more details about sizing: https://www.openproject.org/docs/installation-and-operations/system-requirements
+
+### PostgreSQL database
+
+| Users  | CPU cores | RAM   | disk space |
+| ------ | --------- | ----- | ---------- |
+| <= 500 | 2         | 4 GB  | 25 GB      |
+| 1,500  | 4         | 16 GB | 50 GB      |
+| 3,000  | 8         | 32 GB | 100 GB     |
+
+Database sizing again depends on the workload and average number of queries a user executes, and in most situations, smaller scale will be sufficient for 95% of requests.
+
+### Caching
+
+For production use, OpenProject makes heavy use of caching to reduce hits on the database. We recommend a memcached instance with reserved memory.
+
+| Users  | RAM   |
+| ------ | ----- |
+| <= 500 | 0.5GB |
+| 1.500  | 1GB   |
+| 3.000  | 2GB   |
+
 # Kubernetes
 
 Any self-hosted or managed K8s cluster >= 1.24 listed in