Details
-
Improvement
-
Resolution: Obsolete
-
Medium
-
4.0.1
-
None
Description
On medium to large sites clearing and refreshing view cache on specific actions can take too much time, which results in the user waiting endlessly for the next page to load.
Therefore, the biggest part of the view cache handling should be deferred to cron.
For the user who executed the action that requires heavy cache clearing/refreshing, we can follow two approaches:
- A message can be displayed on each page ("The website is refreshing..." etc.) so he/she knows that the results of his/her actions are not available yet. As soon as the cron job handled the cache refresh we go back to the normal situation. Only for certain nodes we should present him/her immediately with a refreshed cache. For example when the user published a new version of an object the cache of this objects nodes and its parent should be refreshed immediately.
- Serve this user a user-specific view cache (only for this user) as long as the cron job didn't handle the cache refresh.
Attachments
Issue Links
- relates to
-
EZP-10203 Changing classes with a lot of objects can result in a maximum execution time error
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-