-
Improvement
-
Resolution: Fixed
-
Minor
-
2.5.2, 2.6.2
-
MOODLE_25_STABLE, MOODLE_26_STABLE
-
MOODLE_28_STABLE
-
MDL-42071_MK3 -
In load balanced environments, it can be of significant benefit to have memcached servers running on each front end server, as it removes network time for all access of the cache.
Most caches must (or at least really should be) shared, and running caches that point to localhost (ie on each front end) can/will get out of sync, as there is no modification or invalidation between machines.
Some caches have a very low set/hit ratio, like Lang Strings and DB Schema.
With that in mind, I propose a two cache stores (memcachecluster and memcachedcluster) that fetch from one set of servers (typically localhost) and updates a different set of servers (typically the full hostname of each front end).
Because of low set/hit ratio, the time lost in updating multiple servers is more than made up by the gain of fetching locally.
- caused a regression
-
MDL-46796 undefined property error when adding a memcache(d) store
- Closed
- has a non-specific relationship to
-
MDL-46213 Better notification of requirement for clustering memcache/d
- Closed
- has been marked as being related by
-
MDL-42158 Purge additional memcache servers
- Closed
- will help resolve
-
MDL-39837 invalidate cache on multiple servers
- Closed