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

Add some brief information about the type of cache (App, Sess, Req) in the footer

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.9
    • 2.5
    • Caching
    • MOODLE_25_STABLE
    • MOODLE_29_STABLE
    • 39459-29
    • Easy
    • Hide
      1. Ensure performance information is turned on in debugging.
      2. Browse to your site.
      3. Observe that there is now an [a], [s], or [r] after each definition name in the cache stats.
      4. Mouse over each and make sure it tells you what mode it was operating in.
      Show
      Ensure performance information is turned on in debugging. Browse to your site. Observe that there is now an [a] , [s] , or [r] after each definition name in the cache stats. Mouse over each and make sure it tells you what mode it was operating in.

      When using custom instances of caches, it's possible to, for example, create a memcached instance and name it "mymemcached".

      Later you can assign (map) that instance to be used by both application and session caches.

      Then, in the "Caches used (hits/misses/sets)" footer information, there is no way to know which type of cache (Application, Session, Request) is each box. All you get is "mymemcached".

      So this is about to add something, perhaps A, S, R is enough, to know quickly the "mode" each instance is running on each box.

      Not critical, but useful... IMO, for your consideration, ciao

            samhemelryk Sam Hemelryk
            stronk7 Eloy Lafuente (stronk7)
            Ankit Agarwal Ankit Agarwal
            Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
            Andrew Lyons Andrew Lyons
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

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