-
Bug
-
Resolution: Fixed
-
Major
-
2.7
-
MOODLE_27_STABLE
-
MOODLE_27_STABLE
-
w02_
MDL-43524_m27_textcaching -
-
4
-
BACKEND Sprint 9
The trouble is that there is a bazillions of settings/options/conditions that may affect text filter outcomes - it is technically not possible to do a high performance caching at this level.
Dropping the global text caching will fix multitude of issues at the same time:
- JS handling
- use of PAGE and OUTPUT
- use of any other globals
- easier resetting of local filter caches
- etc.
There are already static caches in most filters, which means this should not cause perf regressions on large sites - they were supposed to turn off this ugly feature already...
The next step is to migrate individual filter caches to MUC (unless the perf overhead of MUC
- has a non-specific relationship to
-
MDL-34347 Develop filtered text caching
-
- Closed
-
- has been marked as being related by
-
MDL-44366 filter_glossary has the potential to be slow on large sites
-
- Closed
-
-
MDL-44367 Improve filter_data performance on large sites
-
- Closed
-
-
MDL-44368 filter_activitynames can be improved after dropping of global text cache
-
- Closed
-
- will help resolve
-
MDL-41483 Convert format_text() caching to use MUC
-
- Closed
-