Aportación realizada por Martin Dougiamas

Imagen de Core developers Imagen de Documentation writers Imagen de Moodle HQ Imagen de Plugin developers Imagen de Testers

It's OK to have unshared application caches (directories or memcached)  BUT (and this is a big butt), you (as a sysadmin) need to MANUALLY CLEAR THE CACHES at the right times (for example, every time you upgrade Moodle code).

There is unfortunately no tuning guide for this in our docs, but I am asking our developers to fill this out:   http://docs.moodle.org/25/en/Caching#Cache_definition_configuration    (MDL-41067)

I'd appreciate help from anyone willing to look at the MUC-related code to fill out details in those docs.

Imagen de Core developers Imagen de Documentation writers Imagen de Moodle HQ Imagen de Plugin developers Imagen de Testers

I don't have the data on voting trends but I can assure you that votes on issues are an important factor that I use when deciding what our FRONTEND and BACKEND teams work on.   I don't just look at raw voting numbers either - older issues naturally gather more votes over time even though a newer issue might be more pressing.

(Other factors are: whether it has solution patches; is a security bug; is affecting Moodle Partners; and is part of the major roadmap)

As I'm sure you know, there are always more issues than resources to solve them, and tough choices have to be made all the time.