Loading...

XML

Word

Printable

Details

Type: Story
Resolution: Unresolved
Priority: High
Fix Version/s: 2.3.0-beta1
Affects Version/s: 2.2.1
Component/s: Platform > Persistence > Cache
Labels:
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

EZP-30284 As a v2 User I want optimized cache adapters for better performance

EZP-30298 As a Cluster User I want in-memory cache for all content related lookups

(1 relates to)

Activity

People

Assignee:: Unassigned

Reporter:: André Rømcke (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 28/Jul/18 6:22 PM

Updated:: 20/May/19 2:26 PM