[Bug]: High CPU Load Around 2:00 AM Due to Nextcloud Cron and MariaDB

[qibao07]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

I noticed something similar.

Around 2:00 AM, my server becomes noticeably louder. Looking at the running processes, the main ones are Nextcloud cron and MariaDB, with MariaDB executing some slow queries and using much more CPU.

Checking the CPU load history, this happens almost every day between 2:00 AM and 3:00 AM.

Is there any additional Nextcloud cron job or scheduled maintenance that typically runs during this time?

Steps to reproduce

I then reviewed my historical CPU load data and found that this is not a one-time event. Almost every day between 2:00 AM and 3:00 AM, the CPU load is significantly higher than during the rest of the day.

Expected behavior

Normal low CPU load.

Nextcloud Server version

33

Operating system

Debian/Ubuntu

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?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

*/5 * * * * docker exec -u 33 my-nextcloud php -f /var/www/html/cron.php
*/10 * * * * docker exec -u 33 my-nextcloud php occ preview:pre-generate

[invario]

#59036 possibly the same?

[susnux]

Is there any additional Nextcloud cron job or scheduled maintenance that typically runs during this time?

Yes everything thats time insensitive is scheduled for the maintenance window which you can configure with maintenance_window_start config option. Defaults to UTC 01:00.

Otherwise the load reported here is a duplicate of #59036