sheppy/opendesk
1
0
Fork 0
mirror of https://gitlab.opencode.de/bmi/opendesk/deployment/opendesk.git synced 2025-12-06 07:21:36 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add sizing information for the project management module

Browse Source
This commit is contained in:
Niels Lindenthal
2024-07-18 10:12:30 +00:00
parent 7239df2ec1
commit dfc3188cb7
1 changed files with 38 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
docs/requirements.md
View File

@@ -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