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

$DB->get_records uses a lot of Peak RAM with Postgres (backport of MDL-66327)

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide

      Copied from MDL-66327:

      CI Will test this fully

      I'd recommend that any reviewer and other interested parties uses the dbmemtestcli.php script to compare the different approaches on a variety of hardware and PHP versions.

      Show
      Copied from MDL-66327 : CI Will test this fully I'd recommend that any reviewer and other interested parties uses the dbmemtestcli.php script to compare the different approaches on a variety of hardware and PHP versions.
    • Affected Branches:
      MOODLE_36_STABLE, MOODLE_37_STABLE
    • Fixed Branches:
      MOODLE_36_STABLE, MOODLE_37_STABLE
    • Pull from Repository:
    • Pull 3.7 Branch:
    • Pull 3.7 Diff URL:

      Description

      This fix has been in master for a while and is an important performance improvement. It would be good to get to users (and we certainly want it at the OU!) so I am opening a backport request.

        Attachments

          Issue Links

          will help resolve

          Bug - A problem which impairs or prevents Moodle from functioning correctly. MDL-66327 $DB->get_records uses a lot of Peak RAM (with Postgres)

          • Major - Major loss of function, incorrect output
          • Closed

            Activity

              People

              Assignee:
              timhunt Tim Hunt
              Reporter:
              timhunt Tim Hunt
              Peer reviewer:
              Sam Marshall
              Integrator:
              Sara Arjona (@sarjona)
              Tester:
              CiBoT
              Participants:
              Component watchers:
              Andrew Nicols, Jun Pataleta, Michael Hawkins, Shamim Rezaie, Simey Lameze
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Fix Release Date:
                11/Nov/19

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 30 minutes
                  30m