Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Done
-
None
-
None
-
MXS-SPRINT-184, MXS-SPRINT-185
Description
To minimize the impact of loading of the shard information, the cached could be marked to expire at a certain point in time instead of after a fixed time value. This would make it easier to warm up the caches before peak traffic happens.
An alternative approach to this would be to add a command for manually purging the cache which could then be automated with something like cron.