-
Type:
Epic
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.8.7, 2.8.8
-
Fix Version/s: None
-
Component/s: Gradebook, Performance
-
Labels:
-
Affected Branches:MOODLE_28_STABLE
-
Epic Name:Gradebook performance improvements
In large courses (500+ students) with a decent amount of gradebook entries, a gradebook regrade caused by adding/moving/modifying a grade item can take a really long time, often several minutes.
To test this, extend the testing instructions from https://tracker.moodle.org/browse/MDL-51498 by adding grades to more assignments and monitoring the regrade time after triggering a gradebook regrade. Even in https://tracker.moodle.org/browse/MDL-51498 a 20+ second query time to regrade an almost empty gradebook with 300 grades is unacceptable.
From what I can tell, regrading is very liberal in choosing which grade items to include, and for each included grade item, a grade_grades entry's alteredaggregationweight and alteredaggregationstatus will be written out to the DB at least twice for each user. Once to reset it, and another time to update it. So a gradebook regrade is linear in the amount of grade_grades items present in the gradebook.
- has a non-specific relationship to
-
MDL-51498 Improve performance for regrading gradebook
-
- Closed
-
-
MDL-49324 Recalculating final grades is sometimes necessarily slow
-
- Closed
-
- has been marked as being related by
-
MDL-50589 External gradereport_user::get_grades_table should regrade
-
- Closed
-
- is duplicated by
-
MDL-52854 Gradebook causes database slow down in 3.0
-
- Closed
-
-
MDL-49186 Grade Needsupdate with large recordset
-
- Closed
-
- will be (partly) resolved by
-
MDL-51149 Updating a raw grade triggers full grade recalculation
-
- Closed
-