How many Odoo workers do you need?

Enter the number of people using Odoo at the same moment. The calculator applies the rule of thumb of Odoo's deployment guide and gives you the workers, CPU cores and memory to plan for, with the price of a matching plan.

  • Based on Odoo's deployment guide
  • Workers, CPU and memory
  • Live plan prices

Size your Odoo

Count the concurrent users at your busiest hour, not everyone with a login, and add your integrations: each one sends requests too.

Recommended sizing

20 concurrent users: 4 workers, 2 CPU cores, about 1.6 GB of memory.

  • Workers: 4 · 20 ÷ 6, rounded up
  • CPU cores: 2 · (cores × 2) + 1 covers the workers and 1 cron worker
  • Memory for Odoo: 1.6 GB · 5 processes × about 325 MB on average

Hosted on Knova Cloud

4 workers, 10 GB of storage and 1 staging environment: $308.50 / month (billed monthly). Workers alone: $288 a month. Configure this plan

On your own server

A server with at least 2 CPU cores and 1.6 GB of memory for Odoo, plus room for PostgreSQL and the operating system. Server Pro manages it for $5 a month.

Common team sizes

Concurrent usersWorkersCPU coresMemoryKnova Cloud plan per month
5110.7 GB$92.50
10211 GB$164.50
20421.6 GB$308.50
30532 GB$380.50
50953.2 GB$668.50
1001795.8 GBTalk to us

Rule of thumb from Odoo's deployment guide. It is a starting point: watch the CPU load and response times once you're live, and adjust. Odoo's deployment guide

Where the numbers come from

Odoo's own deployment guide gives three starting points. The calculator applies them and rounds up.

  • Workers: about 1 per 6 concurrent users, rounded up.
  • CPU cores: a server runs at most (cores × 2) + 1 workers, and one of them is for scheduled actions (cron).
  • Memory: 80% light requests at about 150 MB and 20% heavy ones at about 1 GB, per worker, cron included.
  • PostgreSQL, the operating system and the live chat process need their own memory when they share the server.
  • A starting point, not a guarantee: watch the CPU load and response times once you're live, then adjust.

How to size Odoo workers

Four steps from a head count to a configuration you can measure.

  1. Find your peak

    Count the people using Odoo at the busiest hour of the busiest day, such as month-end closing or a busy shop floor.

  2. Add your integrations

    E-commerce connectors, mobile apps and API clients send requests on their own schedule. Count them as users.

  3. Apply the rule

    Divide by 6 for the workers, then check the CPU cores and memory with the guide's formulas, as the calculator does.

  4. Measure and adjust

    Watch CPU, memory and response times after go-live. Add workers when slowness follows the number of people.

Questions about Odoo workers

What is a worker?

A worker is an Odoo process that serves one request at a time on production. More workers let more people use Odoo at once. Most small teams start with one or two and add more as usage grows.

How many Odoo workers do I need?

Odoo's deployment guide estimates about 1 worker per 6 concurrent users, meaning people using Odoo at the same moment, and most small teams start with 1 or 2. Size for your busiest hour, and check requests and response times in the Monitor tab before adding more: one slow action needs profiling, not more workers.

Concurrent users or named users?

Concurrent users: the people whose clicks reach Odoo at the same moment. A team of 40 people with a login rarely has 40 requests in flight, so size for the busiest hour and add your integrations.

Why does the calculator add a worker for cron?

Scheduled actions such as emails, recurring invoices and bank synchronisation run in their own cron worker, which needs CPU and memory too. Odoo's own example counts 8 HTTP workers plus 1 for cron.

Will more workers make a slow action faster?

No. A worker handles one request at a time, so a report that is slow on its own stays slow. Profile that request instead; more workers help when slowness follows the number of people.

Can I change the number of workers later?

Yes. On the Knova Cloud cloud you change the plan and the difference is prorated. On your own server, our installer computes the workers from the server's CPUs and memory and shows you the calculation.

From sizing to a running Odoo

Further reading

The guide behind the rule of thumb, and related reading.

Size it, then run it

Start with the workers you need today and add more when your team grows.

Configure your plan · Ask us