> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/install-cortex-xsoar/post-installation/optimize-performance-and-robustness-from-the-textual-ui/scale-up-hardware-resources.md). # Scale up hardware resources The Scale Settings textual UI menu item enables scaling up resources for CPU, memory, and disk size. Before modifying your environment, it is critical to distinguish between scaling up deployment size and extending storage, as the procedures and downtime expectations differ. **Scaling up deployment size** Scaling up deployment size (CPU & RAM) refers to increasing the CPU cores and RAM to move between scale tiers (for example, Extra-Small → Small → Medium). While Cortex XSOAR allows for scaling, the necessary changes at the hypervisor level (for example, ESXi) often require the VM to be shut down to increase CPU and RAM. Downtime depends entirely on your hypervisor configuration. To scale up the deployment size, first increase the resources on the hypervisor, and then use the **Scan scale** options in the textual UI. {% hint style="info" %} ### Note You can only scale up, you cannot scale down. {% endhint %} **Extending storage (disk capacity)** Extending storage refers to increasing the data disk capacity of existing nodes to accommodate data growth. For most hypervisors (such as VMware), storage can be expanded on a running VM. This operation typically does not require a restart or service interruption. If you extend storage, all nodes in the cluster must be extended equally to keep the cluster healthy. Do not extend disks on only one node. {% hint style="info" %} ### Important The **System Diagnostics** page displays storage usage as a percentage. To view the exact available capacity in GB, you may need to open a support session to run backend command-line tools (such as **`ceph df`**), as these metrics are not currently exposed in the UI. {% endhint %} How to scale up hardware resources 1. Choose the scale you want and make sure your hardware resources meet the system requirements. For more information, see [System requirements](/cortex-xsoar-8-on-prem/8.12/install-cortex-xsoar/system-requirements.md). 2. For CPU/RAM scaling: Shut down the VM (if required by your hypervisor), increase the CPU and RAM allocation, and restart the VM. For storage extension: Expand the disk size in your hypervisor. This can usually be done while the VM is running.

Note

If you are working with more than one node, all the nodes in the cluster must meet the same hardware requirements.

When extending storage, every node's disk must be increased to the exact same size to ensure replication stability.

3. From the textual UI menu, select **Scale Settings**. The supported scale sizes are: * Small: 16 CPU, 64 GB memory, 1 TB hard disk (1TB = 1024 GB) * Medium: 32 CPU, 128 GB memory, 1.5 TB hard disk * Large: 48 CPU, 192 GB memory, 2 TB hard disk ![opp-tui-scale-settings.png](/files/asGepReC99OG5zqM4dE9) 4. Select **Scan Scale Options** to run a scan to evaluate the cluster recommended scale. Based on the results, the system indicates the current scale size and gives you the option to increase the scale size.

Note

The recommended scale is determined by the node with the least hardware resources.

Example 7. The following is the type of system message you may see if you need to add resources to scale up. ![opp-tui-scale-up-message.png](/files/BX5c896MdrXL9ylK9cun) The following is the type of system message you may see if you have sufficient resources to scale up. ![opp-tui-scale-up-message2.png](/files/kWw1FkdcypxvY57XitXh) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/install-cortex-xsoar/post-installation/optimize-performance-and-robustness-from-the-textual-ui/scale-up-hardware-resources.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.