Example server size in three-server environments
You can spread the components across three servers: a database server, application server, and web server. In that type of deployment, the requirements vary depending on the peak loads.
Three-server environments with moderate peak loads
When you have three servers in each environment and moderate peak loads, the server requirements would be as follows:
Environment | Function | CPU cores * | RAM | Disk space | Details |
---|---|---|---|---|---|
Production environment | Database server | 4 | 16 GB | 100 GB | Disk speed requirements: TEXTML Server is heavily I/O bound and
requires a fast disk capable of 200-350 IOPS. The lower value is
acceptable only if the entire docbase can be loaded into memory. Block storage, not mounted CIFS or NFS volumes. |
Application server | 2 | 8 GB | 50 GB | - | |
Web server | 2 | 8 GB | 50 GB | Space required for both applications and users to store files either as a subfolder on the system drive or a separate drive. | |
Test environment | Database server | 4 | 8 GB | 100 GB | Less memory is needed for lower loads and priority. Disk space must still hold the entire docbase. Block storage, not mounted CIFS or NFS volumes. |
Application server | 2 | 4 GB | 50 GB | Less memory needed for fewer simultaneous jobs. (Increases if outputs are large or graphic intensive.) | |
Web server | 2 | 4 GB | 50 GB | Less memory needed for fewer concurrent users. |
* Not counting hyper-threading
Three-server environment with intense peak loads
When you have three servers in each environment and you expect intense peak use, the server requirements would be as follows:
Environment | Server name | CPU | RAM | Disk space | Details |
---|---|---|---|---|---|
Production environment | Database server | 8 | 64 GB | 200-350 GB | Disk speed requirements: TEXTML is heavily I/O bound and requires
a fast disk capable of 600-1000 IOPS. The lower value is acceptable
only if the entire docbase can
be loaded into memory. Block storage, not mounted CIFS or NFS volumes. |
Application server | 4 | 24 GB | 5 GB | - | |
Web server | 2 | 4 GB | 7-8 GB | Space required for both applications and users to store files either as a subfolder on the system drive or a separate drive. | |
Test environment | Database server | 4 | 32 GB | 200-350 GB | Less memory needed for lower loads and priority. Disk space still must hold the entire docbase. Block storage, not mounted CIFS or NFS volumes. |
Application server | 2 | 12 GB | 5 GB | Less memory needed for fewer simultaneous jobs. (Increases if outputs are large or graphic intensive.) | |
Web server | 2 | 4 GB | 50 GB | Less memory needed for fewer concurrent users. |
* Not counting hyper-threading