How can I adjust the resources (CPU, RAM, workers) of my instance?

Is your Odoo instance starting to feel slow, or would you rather cut back the resources given to a rarely used test environment? No need to change plan or wait for us to step in, you can adjust these settings yourself, straight from Hodiploy.

Where to find this setting

1. Log in to Hodiploy from your Client Area
2. Select the instance in your list
3. Click "Edit"
4. Scroll down to the "Instance settings" section

There you'll find the sliders for the CPU, RAM and number of workers allocated to that specific instance. Each instance keeps its own settings, so you can give more power to your production environment than to your test environment, for example.

The ceiling is your server

The sliders stop at the actual capacity of the machine your instances run on: Hodiploy reminds you on screen how many CPUs and GB of RAM your server has, and refuses to save an instance that would ask for more. If you need to go beyond that ceiling, it is the server itself that has to grow, and that is where our team steps in.

Also worth remembering: several instances share the same server. What you give to one is no longer available to the others, so keep some headroom.

How to size the number of workers

The worker count determines how many requests your Odoo instance can handle in parallel. Too low and your instance can slow down under load, too high and it consumes resources for nothing.
Odoo recommends a simple formula.

Number of workers ≈ (Number of CPUs × 2) + 1

For example, with 2 CPUs allocated, you'd aim for around 5 workers. Beyond that guideline Hodiploy warns you: extra workers end up sharing the same cores, so it is better to add CPUs than workers.

Look at the numbers before deciding

No need to add CPU as a precaution. The instance's "Resource usage" screen, in the "Actions" menu, shows what it actually consumed over the last hour, the last 24 hours, the week or the month. A processor topping out every day at the same time tells you far more than a hunch, and a test instance permanently at 3% can hand resources back to the other instances on the server. See how to follow your instance's resource usage.

An important point to keep in mind

Confirming this change triggers a redeployment of your instance so that the new resources take effect. Make sure none of your users are working on it at the time.

If the instance is locked ("Actions" menu, "Lock"), it can be neither edited nor deleted: unlock it first. That is a useful guard rail on a production instance.

Power that grows with your needs

The point of this design is that you're never stuck with your starting configuration. If your business grows, if a client adds users, or if you notice slowdowns at certain hours, you can raise the resources yourself, whenever it suits you. Conversely, nothing stops you from scaling down a development or staging instance that doesn't need as much power as production.

A question about sizing your instance?

If you're not sure which sizing best fits your business, contact us and our team can advise you based on your usage.

Updated on: 24/08/2026