-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't run cron.php for 14min but only 4 #34266
Conversation
Signed-off-by: Marcel Klehr <mklehr@gmx.net>
Yes, on bigger instances it often happens that one execution in parallel is not enough, so we use this to run ~3 in parallel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is intended
I see. On smaller instances it can create high load, though. Wouldn't it be simpler to have the admin add additional entries in crontab if they want higher throughput? |
How so? if there are no jobs, nothing is being done? |
I meant small as in a Raspberry Pi for example. People running nextcloud on there may not have the resources to run 3 cron jobs in parallel. |
Shouldn't we rather recommend to setup multiple cron jobs then? That way admins stay in control on how many parallel processes are running and can adapt that to the available resources. |
Alternatively, this "maximum number of simultaneous cron jobs" should be configurable. |
@nickvergessen On one end we have "resource-constrained systems which can only handle a single simultaneous execution". On the opposite end of the spectrum where there are "resource-rich systems with lots of available cores/parallelism" and "large instances where one execution is not enough". I don't think " |
Apparently cron.php runs for 14min but is called every 5 minutes.
Is there a reason for the discrepancy?
Original issue: nextcloud/recognize#335