Correct configuration to prevent odoo stuck

[fnegrini]

Is your feature request related to a problem? It's been a long time I'm using queue_job module to process jobs in background. Recently, I moved my project to a 8-core ubuntu server VMS in order to increase the paralel jobs. I'm trying to set the best configuration, but no success. I started with 8 workers - 5 for queue jobs. But, when I have all workers for the jobs, Odoo stop responding. I tryied to reduce theese numbers to prevent Odoo stuck. Now I have 5 workers - 3 for queue jobs and Odoo still stuck when I have full jobs.

Describe the solution you'd like Is there a correct way to set theese configuration? Any formula based on CPU count or memory? Is there any other configuration I need to look at?

Describe alternatives you've considered It would be good if you have more detail about documentation in the project.

[amh-mw]

Obligatory link to Odoo configuration sample: https://www.odoo.com/documentation/18.0/administration/on_premise/deploy.html#id6

I moved my project to a 8-core ubuntu server VMS in order to increase the paralel jobs. I started with 8 workers - 5 for queue jobs.

With only eight workers for eight cores, wouldn't any sort of blocking behavior (like database or file access) cause CPU cores to go idle? I would double worker count instead of reducing queue job count.

[fnegrini]

I thought the number of workers should always be lower than the number of CPUs. I will use the formula in the link and return with the results.

[github-actions[bot]]

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.