Fixed
Details
Assignee
Michael OffnerMichael OffnerReporter
Michael OffnerMichael OffnerLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Fix versions
Priority
New
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Michael Offner
Michael OffnerLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Fix versions
Priority
Created 10 October 2023 at 11:35
Updated 24 October 2023 at 09:18
Resolved 24 October 2023 at 09:18
The current solution for flushing the “existing” cache is very simple, it simply checks every 1000 times it adds an element to the cache for invalidated elements in the cache and removes them. That means the elements not necessary get removed if there are not at least 1000 actions.
Instead we should have a “Harakiri“ Thread handling the cache, a “Harakiri“ Thread is a single thread that kills itself when no longer needed.
The new solution should also log (level=debug) what it is exactly doing so we can observe how the cache is growing/shrinking.