System requirements for 0 users
Connection channels
| Web server – DBMS server | 0 Mb/sec |
| Web server – user | Minimum: 0 Mbps Recommended: 0 Mbps |
| Input/output | 0 IOPS |
| Input/output (DBMS server) | 0 IOPS |
Application server
| Environment | Virtual infrastructure |
| vCPU | Number of cores — 0 and more. Maximum number of cores — 16. Frequency 2,6 GHz and more (Haswell gen. or newer) per server |
| vRAM | 8 GB per server |
| HDD (OS) | 60 GB, 100 IOPS, latency less than 10 ms per server
|
| HDD (application) | 20 GB, 100 IOPS, latency less than 10 ms per server |
| Network interface | Number — 1, speed 1 GbE and more |
| Ratio of virtual and physical cores | No more than 2 virtual cores per 1 physical core |
Database server
| OS | Linux Debian 12 |
| Environment | Virtual infrastructure (physical servers preferable) |
| vCPU | Number of cores — 0 and more, frequency 3 GHz and more (Haswell gen. or newer) per server |
| vRAM | 16 GB per server |
| Network interface | Number — 1, speed 0.1 GbE and more |
| Ratio of virtual and physical cores | No more than 1 virtual core per 1 physical core |
Caching server (user sessions)
| OS | Linux Debian 12 |
| Software requirements | Redis Server 7.4 and up |
| Environment | Virtual infrastructure |
| vCPU | Number of cores — 1 and more, frequency 2,4 GHz and more per server |
| vRAM | 2 GB (on Linux) per server |
| HDD | 20 GB, 20 IOPS, latency less than ms (on Linux) per server |
| Network interface | Number — 1, speed 0.1 GbE and more |
| Ratio of virtual and physical cores | No more than 2 virtual cores per 1 physical core |
Marketplace solution requirements
Using of additional Marketplace solutions may affect system requirements. For more information, contact the vendor of the solution.
Implementation recommendations
The main parameter for calculating hardware requirements is the predicted number of users. At the same time, other indicators can affect the performance of the system:
- number of integrations;
- number of sections and pages;
- average number of requests;
- minimum and maximum response time;
- file storage mode;
- average file size, etc.
It is recommended during the implementation of the application to form practical cases with a high load and count performance measurements in conditions close to the real load on the application.
If the load increases, it may be necessary to revise the system requirements.