Server sizing recommendations
This reference gives recommended server sizing for the iGrafx platform application and database servers. The figures are estimates from average customer usage — your needs vary with your use cases and load.
Plan larger deployments directly with iGrafx Professional Services, which evaluates load balancing, clustering, and your specific usage patterns.
Memory and processor
Recommendations by usage level. Parallel users are users performing any action within a 10-second window — not a linear share of total capacity, because the share of simultaneous connections falls as a deployment grows. The estimates assume the application server and database server are on separate machines, which iGrafx recommends.
| User capacity | Parallel users | App server cores | App server memory (GB) | DB server cores | DB server memory (GB) |
|---|---|---|---|---|---|
| < 50 users | 5 | 2 | 4 | 2 | 4 |
| 200 users | 20 | 4 | 6 | 4 | 6 |
| 500 users | 50 | 6 | 8 | 6 | 8 |
| 1,000 users | 80 | 8 | 8 | 8 | 8 |
| 10,000 users | 250 | 12 | 12 | 12 | 12 |
| 20,000 users | 500 | 16 | 16 | 16 | 16 |
Peak-time requirements for the largest installations are hard to estimate. Phase such systems in, and consider clustering so network bandwidth can scale.
Disk space
Recommendations by author count. Documents means both iGrafx documents and other objects (for example Microsoft Word and Excel files). Estimates assume an average file version of 500 KB with up to 50 versions stored.
Disk use depends on the number of authors (for example FlowCharter users), not the total of authors, viewers, and browsers — and it isn't directly proportional to author count, because some new repository documents are shared and linked to existing content rather than added fresh.
| Authors | Estimated documents | App server disk (GB) | DB server disk (GB) |
|---|---|---|---|
| 20 | 400 | 1 | 10 |
| 200 | 3,600 | 1 | 90 |
| 2,000 | 32,000 | 1 | 800 |
| 20,000 | 280,000 | 1 | 7,000 |