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

Expose and encourage use of canuselocalstore in MUC config

    XMLWordPrintable

Details

    • MOODLE_34_STABLE
    • MOODLE_38_STABLE
    • MDL-60341_master
    • Hide
      1. Visit 'Site administration' > 'Plugins' > 'Caching' > 'Configuration'.
      2. In the 'Known cache definitions' look for 'List of available languages'.
      3. Confirm under the column 'Can use local store' it says 'Yes'.
      Show
      Visit 'Site administration' > 'Plugins' > 'Caching' > 'Configuration'. In the 'Known cache definitions' look for 'List of available languages'. Confirm under the column 'Can use local store' it says 'Yes'.

    Description

      The ability for certain cache stores to be local to each front end, ie canuselocalstore = true, has potentially massive performance gains (eg just moving lang strings alone to local can be a big boost). But this is a fairly hidden feature, you can only see this in the cache admin gui when you drill down into each cache store item.

      I'd like to see whether this is true or false for all cache definitions up front on the master muc admin page so you can make sure they are all mapped to local caches where possible.

      Also there is zero moodle dev docs for people implementing cache definitions to allow them to take advantage of this correctly.

      https://docs.moodle.org/dev/Cache_API

      Attachments

        Issue Links

          Activity

            People

              markn Mark Nelson
              brendanheywood Brendan Heywood
              Brendan Heywood Brendan Heywood
              Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
              Jennifer Bauzon Jennifer Bauzon
              Matteo Scaramuccia, Amaia Anabitarte, Carlos Escobedo, Ferran Recio, Ilya Tregubov, Sara Arjona (@sarjona), David Mudrák (@mudrd8mz), Helen Foster, Víctor Déniz Falcón
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                18/Nov/19

                Time Tracking

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