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

Adding indexes in h5p database table

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 3.10.2, 4.1
    • 4.1
    • H5P
    • MOODLE_310_STABLE, MOODLE_401_STABLE
    • MOODLE_401_STABLE
    • MDL-71129-master
    • Hide

      Test with a new Moodle site and a site upgraded from 4.0

      1. As an admin go to Development > XMLDB editor
      2. Click on Load link at 'lib/db' row
      3. Click on Doc link at 'lib/db' row
      4. Go to 'H5P' section (Stores H5P content information)
      5. Confirm a index called 'pathnamehash_idx' exists, not unique and with 'pathnamehash' as Field(s)

      Show
      Test with a new Moodle site and a site upgraded from 4.0 As an admin go to Development > XMLDB editor Click on Load link at 'lib/db' row Click on Doc link at 'lib/db' row Go to 'H5P' section (Stores H5P content information) Confirm a index called 'pathnamehash_idx' exists, not unique and with 'pathnamehash' as Field(s)
    • HQ Sprint 0.3 Database

    Description

      In order to optimizing our database performance, we have found the SQL Query called in the function get_content_from_pluginfile_url in h5p-plugin:

      SELECT * FROM `mdl_h5p` WHERE `pathnamehash` = ?

      This query took almost 1minute for approximately 6 execution. We want to put an index on the field pathnamehash. Is that a good solution? or does anyone have any idea?

       

      Attachments

        Issue Links

          Activity

            People

              nisadoc nisaDoc
              nisadoc nisaDoc
              Ilya Tregubov Ilya Tregubov
              Jun Pataleta Jun Pataleta
              Angelia Dela Cruz Angelia Dela Cruz
              Amaia Anabitarte, Carlos Escobedo, Laurent David, Sabina Abellan, Sara Arjona (@sarjona)
              Votes:
              2 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                28/Nov/22

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour, 38 minutes
                  1h 38m