Minimum resource prerequisites for Sage X3 V12
These minimum resource prerequisites concern Sage X3 with standard modules and parameters.
Each requirement corresponds to a component of the Sage X3 stack. The minimum resource prerequisites of an individual Sage X3 server are calculated by combining all server components' requirements.
You need to increase the following figures in case your Sage X3 installation supports transactions are generated by non-interactive users such as web services or batch jobs.
Note: One user corresponds to one user session with one tab open. If users open multiple tabs, more resources are required for the server to work correctly.
Sage X3 Server
| Configuration | Less than 30 users | Between 30 and 60 users | Between 60 and 120 users | Comments | |||||||||
| Component | CPU | RAM | Disk | Network | CPU | RAM | Disk | Network | CPU | RAM | Disk | Network | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| OS | 0.5 cores | 2 GB | 32 GB | 10 GB/s 500µs TCP latency | 0.5 cores | 2 GB | 32 GB | 10 GB/s 500µs TCP latency | 1 core | 2 GB | 32 GB | 10 GB/s 500µs TCP latency | For the disk, the minimum read speed should be 125MB/s and it should allow 1500 input/output operations per second (IOPS) per volume. |
| Database | 1 core | 4 GB | 40 GB | - | 2 cores | 8GB | 80 GB | - | 4 cores | 16 GB | 160 GB | - | - |
| Application | - | - | 40 GB | - | - | - | 80 GB | - | - | - | 160 GB | - | - |
| Runtime | 1 core | 3 GB | 1 GB | - | 2 cores | 6 GB | 1 GB | - | 4 cores | 12 GB | 1 GB | - |
The runtime allows one web session and one classic session to coexist. It takes into account if a batch session is running or not. For each session, 100 MB of bandwidth are available. |
| MongoDB | 0.25 cores | 1 GB | 4 GB | - | 0.25 cores | 2 GB | 4 GB | - | 0.5 cores | 4 GB | 8 GB | - | - |
| Syracuse | 0.25 cores | 1 GB | 2 GB | - | 0.5 cores | 2 GB | 2 GB | - | 1 core | 4 GB | 4 GB | - |
A minimum of two nodes are required for web and REST services. One node per 30 users. 1 GB per node. 0.5 CPU cores per node. |
| Syracuse web services (5 channels) | 0.25 cores | 1 GB | - | - | 0.25 cores | 1 GB | - | - | 0.5 cores | 2 GB | - | - |
A minimum of two nodes are required for SOAP services. One node per process. 0.5 CPU cores per process. |
| Print server | 0.75 cores | 2 GB | 4 GB | - | 2 cores | 4 GB | 4 GB | - | 4 cores | 8 GB | 8 GB | - |
For the CPU and RAM, the ratio of print server jobs to users is one to 15. For 30 users, two print server jobs run in parallel; for 60 users, four print server jobs; for 120 users, eight print server jobs. By default, five print server jobs run in parallel. For the disk, it depends on the logs and error trace sizes. Leveraging the Windows print spooler when the Sage X3 report output is sent to a printer can cost more CPU and memory resources than executing the Sage X3 print server engine. Therefore, the Windows spool system's needs are not taken into account for resources prerequisites. |
Other components
| Configuration | Less than 30 users | Between 30 and 60 users | Between 60 and 120 users | Comments | |||||||||
| Component | CPU | RAM | Disk | Network | CPU | RAM | Disk | Network | CPU | RAM | Disk | Network | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Console (Basic actions) | 0.25 cores | 0.50 GB | 0.50 GB | - | 0.25 cores | 0.50 GB | 0.50 GB | - | 0.25 cores | 0.50 GB | 0.50 GB | - | You can find console logs under the Windows user profile. |
| Console (Application configuration) | 1 core | 2 GB | 1 to many | - | 1 core | 2 GB | 1 to many | - | 1 core | 2 GB | 1 to many | - |
When the remote import between two solutions option is activated, the folder archive goes through the server where the console is being used. When the parallel import/export option is activated, you can access multiple cores on the distant server such as the runtime and the database. |
| Elasticsearch | 2 cores | 4 GB | 4 GB | - | 2 cores | 4 GB | 4 GB | - | 2 cores | 4 GB | 4 GB | - | Elasticsearch is optional. |