Details
-
Story
-
Resolution: Unresolved
-
High
-
2.2.1
-
None
Description
As a developer, especially core developer, it would be helpful to see which code is triggering calls to uncached SPI\Persistence methods in order to identify if calling code can be optimized or not.
However we don't need full trace which would be make the overview unreadable, we just need the relevant calls in Repository and the class that called kernel.
Attachments
Issue Links
- relates to
-
EZP-30350 As a Developer I want in-memory to not break BC for cache clearing
- Closed
-
EZP-30335 As a Developer I want in-memory cache to clear cache using LFU approach
- Documentation Done
-
EZP-30340 As a Developer I want in-memory cache for User Preferences
- Documentation Done
-
EZP-29659 As a v2 Developer I want support for InMemory SPI cache
- QA
-
EZP-30284 As a v2 User I want optimized cache adapters for better performance
- QA
-
EZP-30298 As a Cluster User I want in-memory cache for all content related lookups
- QA