Forum Discussion
How to understad "Aging rate" in Webacceleration
I have some doubt.
eg:2 webacceleration policies used by 2 virtual servers.
policies_1: max cache size : 50mb, aging rate:0 policies_2: max cache size : 50mb, aging rate:5
If policy_1'memory is full, which entry whill be freed???
If policy_1's entry will be free,there is no sense to use "Aging rate" because all the entries in policy_1 use the same priority(Aging rate).
If policy_2's entry will be free, it's useful to reduce memory of policy_2 accurately, but the memory of policy_1 is still full.
3 Replies
- mrpre_179829
Nimbostratus
policies_1: max cache size : 50mb, aging rate:0 policies_2: max cache size : 50mb, aging rate:5 - mrpre_179829
Nimbostratus
"max cache size " refer to the "Cache size" in Cache Settings. - Brad_Parker
Cirrus
"The comparative age of an object is one of several factors, including hit rate and priority, that together determine which objects are removed from the cache when space is needed for new objects. The aging rate setting controls how much relative weight is given to age versus these other factors when performing the calculation."
https://support.f5.com/kb/en-us/solutions/public/14000/300/sol14333.html
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com