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

Ability to localize databasemeta MUC

XMLWordPrintable

    • MDL-66146_master
    • Hide

      If your stack has immutable fronts ends, eg static containers which are locked to a version, then you can just create an APCu muc store and put this data into it safely, ie without any  revnumber handling at the code level.

      This tracker only really has value in terms for stacks where the code is upgrade in places, and where you want the cache gui to correctly reflect that this is localizeable.

      Show
      If your stack has immutable fronts ends, eg static containers which are locked to a version, then you can just create an APCu muc store and put this data into it safely, ie without any  revnumber handling at the code level. This tracker only really has value in terms for stacks where the code is upgrade in places, and where you want the cache gui to correctly reflect that this is localizeable.

      About 25% of the traffic to muc is for the databasemeta store which we think can safely be localized and pushed to say APC instead.

      It should be more or less like the other local caches with eg themerev, but might have a slight chicken and egg thing with using the db to get a cacherev number to then use the db. I don't think it will end up being a big deal.

            Unassigned Unassigned
            brendanheywood Brendan Heywood
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:

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