Details
-
Improvement
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
Description
Step to reproduce flush cache performance issue in 6.2:
- Running with dx-core-demo-webapp version 6.2-SN
- Enable cache per site via setting /modules/advanced-cache/config@createseparatecachesforeachsite to true. Refer here for detail about multi site cache configuration
- Any changes in the site or advanced-cache require restarting the advanced-cache module and re-registering multiple observations. Specifically, for each site, there are 24 observations listening to the root path of workspaces and monitoring event changes, which then trigger the flush policy. For more detailed information, please refer to the link to access the detailed log
- 24 workspace per site are:
dam keystore contacts usergroups scripts tours website userroles campaigns stories workflow tags userranking visitors tasks category segments rss personas resources default pendingContacts marketing-tags config
Expectation: list out some workspace like userranking, rss, pendingContacts, personas.. need to add to excludedWorkspaces property by default.
To me: important workspace need to listen per site can be: website. For others workspace we can be get via defaultPageCache?
- Ex: A strange thing I noticed in the userranking workspace is that it has functionality to store data to JCR every 1 minute. So flush cache policy for userranking workspace always call every 1 minute.
- See their code: UserRatingsManager.java#44, JcrUserRankerStorage.java#100
Checklists
Acceptance criteria