Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-66328

Groups overview runs out of memory on very large courses

XMLWordPrintable

    • MOODLE_36_STABLE, MOODLE_37_STABLE
    • MOODLE_36_STABLE, MOODLE_37_STABLE
    • Hide
      1. Use Admin -> Development -> Make test course to generate an XL or XXL course.
      2. Ensure that Admin -> Development -> Debugging -> Show performance info is turned on.
      3. Go to Course setting -> Users -> Groups -> Groups overview.
      4. Verify that the page displays (rather than an out-of-memory error).
      Show
      Use Admin -> Development -> Make test course to generate an XL or XXL course. Ensure that Admin -> Development -> Debugging -> Show performance info is turned on. Go to Course setting -> Users -> Groups -> Groups overview. Verify that the page displays (rather than an out-of-memory error).

      The groups overview is running out of memory on one of our very large courses.

      I think that is mostly caused by MDL-66327 which will be helped by changing the $nogroupusers = $DB->get_records_sql($sql, $params); line to a get_recordset.

      Also, since this is a large report, it might be reasonable to allow it MEMORY_EXTRA.

        1. MDL-66328.png
          MDL-66328.png
          53 kB

            timhunt Tim Hunt
            timhunt Tim Hunt
            Sam Marshall Sam Marshall
            Andrew Lyons Andrew Lyons
            Jennifer Bauzon Jennifer Bauzon
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 hours, 10 minutes
                2h 10m

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.