> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/servers-1/concepts/size-cpu-ram-disk.md).

# Right-size your server

Sizing a server means deciding three things: how much **CPU**, how much **RAM** and how much **disk** your client's workload needs. You don't have to get it right the first time: you adjust the size whenever needed, without reinstalling.

> #### 📘 Key idea
>
> Start with what the workload needs, not what you think it will need someday. You pay for consumption and scale up live, so oversizing from the start only makes the bill more expensive.

### The three pieces

* **vCPU** — the computing power, based on Intel Xeon processors. More vCPUs mean more capacity to process in parallel.
* **RAM** — working memory. It determines how many processes and how much data the server handles at once without relying on disk.
* **Disk** — storage. You start with an NVMe system disk (from 60 GB) and add data disks as needed; each one includes backup.

You choose combinations from **1 vCPU / 1 GB** to **32 vCPU / 128 GB**.

### The balance between CPU and RAM

Not all workloads require the same ratio. A service that does a lot of computing needs more CPU; one that moves a lot of data in memory — a database, for example — needs more RAM. That's why the sizes combine both in different ratios, from 1:1 to 1:4 or more: you choose the one that fits your workload, not simply "more of everything".

### How to choose according to the workload

A rough starting point, depending on what you use the server for:

| Typical workload                           | Starting point   |
| ------------------------------------------ | ---------------- |
| Light services (DNS, proxy, microservices) | 1 vCPU / 1–2 GB  |
| Web, CMS or small apps                     | 1 vCPU / 4 GB    |
| ERP, CRM and business applications         | 2 vCPU / 4 GB    |
| Databases, SQL Server                      | 4 vCPU / 8 GB    |
| Virtualization or heavy workloads          | 8 vCPU / 16 GB   |
| Analytics and large volumes                | 16 vCPU / 32 GB  |
| SAP or demanding databases                 | 32 vCPU / 128 GB |

In an ERP, the number of users also determines the size: the more concurrent users, the more CPU and RAM. The full catalog of sizes is in [Details.](/docs-en/productos/servers/details.md)

### Start lean and scale

When a server runs short, you add **CPU, RAM or disk live**, without reinstalling or migrating anything. Expanding the disk does not stop the server; shrinking it is more delicate and should be planned (you have it step by step in How-to).

That way you work: you start with the size the workload needs today and grow it at your client's business pace.

### Next steps

* Choose the operating system in [Images and applications.](/docs-en/productos/servers/concepts/images-and-applications.md)
* Design connectivity in[ Server networking.](/docs-en/productos/servers/concepts/networks.md)
* Create your first server with [Quick Start](/docs-en/productos/servers/quickstart.md)

<br>


---

# 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://docs.plenit.com/docs-en/productos/servers-1/concepts/size-cpu-ram-disk.md?ask=<question>&goal=<endgoal>
```

`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.