System Requirements & Sizing
Overview
- The following information is derived from the mID Server load tests in context of the PostGreSQL implementation.
- 100 Login/s is the highest known stable function with PostGre SQL.
Minimum Setup
The minimum setup (0 Logins/s) is the smallest runnable configuration (e.g. for test, development etc. environments).
IMPORTANT: The login/s is the relevant scaling parameter. For better visibility, the number of users has been added from KOBIL experience with our customer projects. This setup assumes high availability in the sense that there shall be no interruption in backend service if on pod crashes. Therefore 2 pods per component have been assumed for this setup. If the delay between pod crash and restart via Kubernetes/Openshift is acceptable the installation the resources can be further reduced.
| Number of end user (Login/s) | Number of end user (Login/s) | ||
|---|---|---|---|
| Application | Resources | 0 (0 Login/s) | 100.000 (2 Login/s) |
| KOBIL Application (mID Provider + mID Server). HA setup with 2 minimum pods for each component for high availability | Cores total (Openshift/Kubernetes Cluster) | 6 | 10 |
| RAM total (Openshift/Kubernetes Cluster) | 10 GB | 15 GB | |
| HDD total (Openshift/Kubernetes Cluster) | <20 GB | <20 GB | |
| Database (Sample: postGreSQL) | Cores | 2 | 2 |
| RAM | 6 GB | 6 GB | |
| HDD | 10-30 GB HDD per year for records | 10-30 GB HDD per year for records |