Sizing
Last updated
Last updated
Sizing is a crucial aspect of the IT infrastructure planning process, which involves determining the appropriate resources needed for optimal performance and scalability. In the context of IT-Conductor, sizing refers to understanding the requirements of your environment, such as the number of systems, databases, and applications to be monitored, to ensure that the solution is properly sized to meet your specific needs.
The sizing guide provided below offers valuable insights and recommendations to help you accurately assess and allocate the necessary resources for a successful implementation.
This sizing technique uses t-shirt sizes (XS, S, M, L, XL) under the assumption that having an estimate is better than none. It can be useful for the budget planning phase even when figures may not be clear, assumptions can be made, and validation can occur later.
Now, think of these t-shirt sizes as hardware requirements where XS requires the least amount of power/memory/etc. and XL requires the most.
To make things much easier, we developed the IT-Conductor Sizing Table based on the T-Shirt Sizing principle to guide you in your sizing exercise.
T-Shirt Size | CPU (Core) | Memory (Gb) | Landscape (System) |
---|---|---|---|
XS | 4 | 4 | <=25 |
S | 4 | 8 | <=50 |
M | 4 | 12 | <=75 |
L | 8 | 16 | <=100 |
XL | 8 | 32 | >100 |
IT-Conductor production Gateway should have a standby/failover Gateway VM of the same size to ensure service resiliency and meet IT-Conductor Service Level Agreement requirements.
Note: The rule of thumb is 25 systems per 4CPU 4GB. Then add 4GB memory for the next 25 systems. CPU is not usually a constraint.