Timed-based background jobs

[AndyScherzinger]

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
Some background jobs are long-runners and create heavy load, this can also happen during office hours impacting the system's performance for users during such times.

Describe the solution you'd like
Provide a way to define a time when a background job should run.
e.g. to ensure heavy load jobs don't run during office hours but rather at night.

Describe alternatives you've considered
none

Additional context

[PVince81]

Concept, as discussed with Joas and Robin:

• add column that says time sensitive vs non-time sensitive
• job implementors need to decide whether their job is time-sensitive or not (statically), suitable for jobs that run once or twice a day
  • deleting activities
  • file retention
  • suspicious login
  • preview cleanup
• recommend to have a 4h window
• off by default because we can't guess timezone, and recommend admins to enable it
• when enabled, setup hours when expensive jobs should not run (or start time)
• when getting next job, filter in or out based on current time
• no sorting, just filtering
• will only work for system cron: because all the other modes cannot guarantee. If any other mode is set, it will default to the non-time-range behavior.

[PVince81]

PR here: #30945

[AndyScherzinger]

pinging @ChristophWurst to check if this would then fit your view of using this to implement the mail adoption, else best to align with the files team

[ChristophWurst]

mail adoption

can you tell me which one specifically? We can certainly move any cleanup job. But inbox synchronization should remain an hourly job so when you open the app the cache is somewhat up to date.

I've opened nextcloud/groupware#28 for our team.

[AndyScherzinger]

@ChristophWurst no idea tbh, it is referenced in some place in general and I believe given the cross reference for mail scheduling the outlined approach won't be an enabler for implementating scheduled mail sending.

[nickvergessen]

can you tell me which one specifically? We can certainly move any cleanup job. But inbox synchronization should remain an hourly job so when you open the app the cache is somewhat up to date.

Yeah it's mostly about the "daily" things. Priority scanning comes to mind or pruning data

[blizzz]

that's done, afaik?! closing.