Details
-
Improvement
-
Status: Waiting for integration review
-
Major
-
Resolution: Unresolved
-
Future Dev
-
None
Description
This is the root cause here where it queries the log, and does that query inside a loop once per course. With a huge number of courses and a huge log table this is huge bottle neck.
I'm proposing to radically simply this to:
- have a moodle event handler looking for any changes to course events
- if found, then just set a 'course has modifications' flag
- the backup tasks will look at this flag when scheduling the automated backups and reset the flag when they are done
This change depends on MDL-73926, so the commit is based on it. It will be rebased once MDL-73926 gets accepted.