# Sizing
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.
### T-Shirt Sizing Technique
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.
Figure 1: T-Shirt Sizing Technique
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.
Figure 2: T-Shirt-to-Hardware Sizing Equivalent
### IT-Conductor Sizing Table
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.
{% hint style="info" %}
**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.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.itconductor.com/overview/architecture/sizing.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.