You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The decision to write the jobrunner was made very early on. In my understanding, it was designed to allow fast parallel execution of background jobs in multiple channels, also allowing a hierarchy of channels.
However, I'm asking myself why not offer users the alternative to use ir.cron to run jobs. That would look as follows:
Each channel has a corresponding ir.cron record, disabled by default
These crons trigger periodically eg. every 1 minute or 5 minutes (configurable)
When triggered, the cron start a loop to processing jobs assigned to the channel, just like the jobrunner does. The loop can be configured to run a maximum of eg. 100 times or 1000 times (configurable) before it stops and waits to be triggered again. Of course, a database commit would run after each iteration.
What would be the benefits or problems with such an approach?
The decision to write the jobrunner was made very early on. In my understanding, it was designed to allow fast parallel execution of background jobs in multiple channels, also allowing a hierarchy of channels.
However, I'm asking myself why not offer users the alternative to use
ir.cron
to run jobs. That would look as follows:ir.cron
record, disabled by defaultWhat would be the benefits or problems with such an approach?
Benefits I can think of:
server_wide_modules
or special Odoo settingsDownsides:
max_cron_threads
would have to be high enough, warn user if he exhausts themThe text was updated successfully, but these errors were encountered: