Open MiningPickaxe opened 1 year ago
Are you the only user or do you have other users on your server? The biggest variable that plays a role probably in this job run is driven by your environment's users' external calendar subscriptions:
https://docs.nextcloud.com/server/latest/user_manual/en/groupware/calendar.html#subscribe-to-a-calendar https://docs.nextcloud.com/server/latest/admin_manual/groupware/calendar.html#subscriptions
Do you Nextcloud logs contain any notable entries during the period of these job runs?
Related enhancement request: #36849 (just noting for future reference)
⚠️ This issue respects the following points: ⚠️
Bug description
During the cronjob run there is excessive load on the database, the cron run takes about 10 minutes. I also generate 100-200mb of binlogs per minute.
When checking the oc_jobs table to see what takes so long this is the output:
The time needed for the RefreshWebcalJob seems to be extremly high. There are also constantly high writes to the mariadb binlogs:
I needed to set up a cronjob that purges the old bin logs regularly to keep up with the amount of logs generated and not make the system explode instantly.
Steps to reproduce
I don't really know how to reproduce this, it just happens on my server when running the
sudo -u www-data php -f /var/www/nextcloud/cron.php
Expected behavior
I would expect the cron to run in a reasonable amount of time (which it did when first setting it up, I don't know when it got worse).
Installation method
None
Nextcloud Server version
25
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response