LAST UPDATED MAY 2022

For planning purposes, you should start with 1 worker per: 

• 25 users or 
• 5,000 daily visitors. 

The resources Odoo uses can vary a great deal depending on:

• what features are available 
• how often they are used
• balance of user / visitor ratio
• spread of visitor count over time (steady), vs concentrated (surge)
• how much CUSTOM code has been installed

Given this, you only really know how many Workers you need when you are live, so should be monitoring your performance prior to go live, during testing, and after go live in case you need to rollback to a point where performance was not an issue.

In addition to using logging (and looking at log files) we provide RESOURCE MONITORING features with Odoo.sh:

• performance analysis and CPU visualization (flamegraph)
• system, http and mail monitoring (grafana)

With this in mind:

1 worker is about 6 concurrent users.

ie: ALL clicking a button at the "exact same time".  

Up to 99% of the time users read, type or scroll and that does not count as 'using' Odoo since no server resources are consumed.  Only when a User or Visitor clicks a button, runs a report, imports data, etc. are server resources consumed.

Considerations:

• Using Odoo once a day for time sheets is considered EXTREMELY LIGHT use
• Using Odoo all day long without a break is considered EXTREMELY HEAVY use. 
• Most are somewhere in between so test LIGHT, MEDIUM and HEAVY use scenarios.
• 1 worker could support 50 users or 100 users, depending on the scenario.
• 1 worker could support 10,000 an day or 5,000 an hour, depending on the scenario.   

The great thing about Odoo.sh is that extra workers are not hard to add.