|
|
| Participants: |
Dan Poltawski and Petr Skoda
|
| Security Level: |
None
|
| Affected Branches: |
MOODLE_19_STABLE
|
| Fixed Branches: |
MOODLE_19_STABLE
|
|
I have some sample data & when uploading 165 user records with this sort of thing:
username,course1,course2,course3,course4,course5,group1,group2,group3,group4,group5
myusername,9.1,9.2,9.3,9.4,9.5,9H,9H,9H,9H,9H
myusername2,9.1,9.2,9.3,9.4,9.5,9H,9H,9H,9H,9H
Its costing 16,000 database queries. This makes the upload unusuable.
Need to investigate and improve what is causing this.
|
|
Description
|
I have some sample data & when uploading 165 user records with this sort of thing:
username,course1,course2,course3,course4,course5,group1,group2,group3,group4,group5
myusername,9.1,9.2,9.3,9.4,9.5,9H,9H,9H,9H,9H
myusername2,9.1,9.2,9.3,9.4,9.5,9H,9H,9H,9H,9H
Its costing 16,000 database queries. This makes the upload unusuable.
Need to investigate and improve what is causing this. |
Show » |
|
Bug
Open
Major
Bulk upload user form costs 16,000 database queries with 165 users course/group enrolments
// make sure user is enrolled into course before adding into groups
if (!has_capability('moodle/course:view', $coursecontext, $user->id, false)) { $upt->track('enrolments', get_string('addedtogroupnotenrolled', '', $gname), 'error'); continue; }
Some sort of course participant cache would help here