You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/10/13 11:09:00 UTC
[jira] [Work logged] (WW-5355) Use LRU cache by default
[ https://issues.apache.org/jira/browse/WW-5355?focusedWorklogId=885012&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-885012 ]
ASF GitHub Bot logged work on WW-5355:
--------------------------------------
Author: ASF GitHub Bot
Created on: 13/Oct/23 11:08
Start Date: 13/Oct/23 11:08
Worklog Time Spent: 10m
Work Description: kusalk opened a new pull request, #766:
URL: https://github.com/apache/struts/pull/766
WW-5355
--
I see very limited advantage to using the default cache over the LRU one? The eviction process is faster but at the cost of having to repopulate the whole cache from scratch!
Keen to hear other thoughts or anything I may have missed
Perhaps in the future we can move to a more advanced algorithm such as the ones provided by [Caffeine](https://github.com/ben-manes/caffeine/wiki/Efficiency), although I'm not sure how effective they'd be given the cache can be easily attacked.
Issue Time Tracking
-------------------
Worklog Id: (was: 885012)
Remaining Estimate: 0h
Time Spent: 10m
> Use LRU cache by default
> ------------------------
>
> Key: WW-5355
> URL: https://issues.apache.org/jira/browse/WW-5355
> Project: Struts 2
> Issue Type: Improvement
> Components: Core
> Reporter: Kusal Kithul-Godage
> Priority: Minor
> Fix For: 6.4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)