Updates to grade caching system and other utility scripts #262
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… using file store for caching.
…tion avoiding code
in preparation for Moodle 5.0...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates to the grade caching to make it work better and to make it play nice with Moodle 5.0.
Other utility scripts (eg, bulktester, cachepurger, etc) also updated to be even more handy (and Moodle 5.0 friendly).
The scheduled cachecleaner task now only runs if the grade cache is enabled and is now explicitly only for a file store cache backend. The Redis cache cleaner can be used if cleaning is needed for Redis.
The gradecache is still experimental and hasn't been fully tested on Redis. So, if you're going to use it, we recommend sticking to a file store backend for it.