Details
-
Story
-
Resolution: Unresolved
-
High
-
2.5.0-rc1
Description
As a System Administrator & Developer I'd like SPI cache to re-introduce support for in-memory cache.
However unlike 1.x it must be:
- limited to not eat up all available memory
- time limited so data does not risk becoming stale
This allowing it to be used also on long running command line scripts without need to document special ways to run scripts.
As it it to be limited it should alos be:
- preferring to use available space for non content cache (meta data) which is frequently needed by the system, and in-frequently changed
Attachments
Issue Links
- is cloned by
-
EZP-30284 As a v2 User I want optimized cache adapters for better performance
- QA
- relates to
-
EZP-29470 As a developer I want trace for uncached Persistence calls
- QA
-
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-30006 As a Developer I possibility to load several languages at once
- QA
-
EZP-30298 As a Cluster User I want in-memory cache for all content related lookups
- QA
-
EZP-29821 As a Developer I want less SPI calls to be done by Admin UI
- Closed