[EXTIDX-9] Caching should not cache forever Created: 14/Sep/11  Updated: 16/Mar/23  Resolved: 16/Mar/23

Status: Closed
Project: External Indexing (closed)
Component/s: Core
Affects Version/s: None
Fix Version/s: 1.0

Type: Task Priority: Critical
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

The current implementation of CachingSimilarService uses Magnolia's cache, which unfortunately can only have one cache configuration, which means for now, the cache configuration is the same as for pages, which isn't ideal. We should cache search results for less long, and/or based on usage (evict LRUs), etc.

See http://wiki.magnolia-cms.com/display/DEV/Concept+-+Cache+Improvements#Concept-CacheImprovements-Cacheconfiguration for a few notes.



 Comments   
Comment by Magnolia International [ 20/Sep/11 ]

Additionally, having this would mean we could come up with a solution that "caches results until remote server is available again". Now, if we flush the cache-of-results every N minutes, we're entirely dependent on the remote server's availability.

Comment by Adam Jones [ 16/Mar/23 ]

Closing due to project being archived.

Generated at Mon Feb 12 01:56:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.