Review background jobs for potential TIME_INSENSITIVE switch

[juliusknorr]

With nextcloud/server#30945 it will be possible to move background jobs to times where the server is less busy. We have some tasks that currently run at a fixed interval, where it might make sense to move them for the chance of yielding better performance.

To do

• Find out which of our background jobs are not time critical
• Move them

Affected apps

• text https://github.com/nextcloud-gmbh/server/issues/106#issuecomment-1044300427
• richdocuments https://github.com/nextcloud-gmbh/server/issues/106#issuecomment-1044300427
• collectives https://gitlab.com/collectivecloud/collectives/-/merge_requests/480
  • https://gitlab.com/collectivecloud/collectives/-/blob/main/lib/BackgroundJob/ExpirePageVersions.php
  • https://gitlab.com/collectivecloud/collectives/-/blob/main/lib/BackgroundJob/PurgeObsoleteCollectives.php
  • https://gitlab.com/collectivecloud/collectives/-/blob/main/lib/BackgroundJob/PurgeObsoletePages.php
• office online (unchanged - same as richdocuments)
• deck
  • https://github.com/nextcloud/deck/blob/master/lib/Cron/CardDescriptionActivity.php - unchanged
  • https://github.com/nextcloud/deck/blob/master/lib/Cron/DeleteCron.php Move DeleteCron to be time insensitive deck#3599
  • https://github.com/nextcloud/deck/blob/master/lib/Cron/ScheduledNotifications.php - unchained

[juliusknorr]

@mejo- Regarding the collectives background jobs, they all sound non-time critical, so we could potentially migrate those to become time insensitive with nextcloud/server#30945 Can you check that?

[mejo-]

Thanks for raising this @juliushaertl. Indeed, all collectives background jobs are time-insensitive. I implemented this now in https://gitlab.com/collectivecloud/collectives/-/merge_requests/480. If you could give it a quick review, I'll merge straight away 😊

[juliusknorr]

Thanks for taking care @mejo-