RAM cache and prefetch
![[Deleted User]](https://w2.vanillicon.com/v2/2bb29d357b97c8440eefe2439893b4f2.svg)
Posted by jmaddox
What is AX behavior in the case of expired object in RAM cache? Does AX proactivley request object from server? Or doe it wait for the next request for that object? There are pros and cons to each behavior.
What is AX behavior in the case of expired object in RAM cache? Does AX proactivley request object from server? Or doe it wait for the next request for that object? There are pros and cons to each behavior.
0
Comments
When an object expires from the AX cache, then AX won't proactively request it.
This one will be requested when 1 new user will ask for it.
I see plenty of PROs with such behavior. Let's take an example:
. User1 asks for Object1
. AX cache it + deliver it to User1
. Then nobody else alsks for that object
. After some period of time, that object is deleted from the cache:
. 1h (default value)
. or less if the web server told us the object is cacheable for less than 1 hour
. or less if the cache was full
Note: When the AX cache is full and needs to cache a new object, AX deletes the object that wes requested the least amount of time (not the oldest one)
At that time (when the object is deleted), I don't want the AX to ask proactively for that object again since I don't know if it will be popular in the future and waist AX cache space if that object is not popular.
Can you help me with the CONs, because I can't find one?
Dimitri
Thanks for the clarification.
the explained behavior clears up the cons.
con for default ax behavior.
-high traffic sights with low cache expire could benefit from periodic refresh from load balancer.
note: explained behavior seems more optimal.
con for prefetch:
- as explained in your response.