Eviction Policy
If a cache reaches its maximum storage limit and eviction is turned on, the specified ratio of items will be evicted to make space for new objects. On the other hand, if cache reaches its maximum storage limit and eviction is turned off, items are neither evicted nor added to the cache any further.
An eviction scheme is used to select the objects that need to be removed from cache. A particular eviction policy can be selected at the creation time but once it is set it cannot be altered in the running cache. User can change eviction policy after creating a cache only if it is not running. Three types of Eviction Policies are provided by NCache:
- Least Frequently Used
This feature is only available in NCache Enterprise Edition.
In this scheme a counter that counts the access made to an object is used. At the time of eviction objects with lowest counter number are evicted first. Here too a random selection is made between two objects with same counter.
- Least Recently Used
This feature is only available in NCache Enterprise Edition.
This eviction scheme associates a timestamp with all objects. This timestamp is updated each time the object is accessed. When evicting, objects with the oldest timestamp are picked first. In case of two objects with the same time stamp, a random selection is made.
- Priority Based Eviction
This is the default eviction policy and has the same mechanism as LFU with the addition of a relative cost that is associated with an object at the time of its addition to cache. Objects with lower cost are removed before objects with higher cost. Client application can choose from a list of priorities that is predefined (Low, Below Normal, Normal, Above Normal, High and Not Removable). In case a priority is not chosen, it is set by default as Normal.
These eviction policies for a cache can be specified in one of the following two ways.
Using NCache Web Manager
Launch NCache Web Manager by browsing to
http://localhost:8251(Windows) or<server-ip>:8251(Windows + Linux).In the left navigation bar, click on Clustered Caches or Local Caches, based on the cache server to start. Against the cache name, click on View Details.
This opens up the detailed configuration page for the cache.
In the Overview tab, click on the
button.Check the Enable Eviction box.
Select the Policy from drop down list.
If you have selected Priority based eviction, then Default Priority can also be changed in the drop down list.
Change the Percentage if required.
Click on
to save the cache configuration.
Manually Editing NCache Configuration
Important
Make sure the cache is stopped before making any configuration changes.
- Specify the Eviction Policy for a cache through config.ncconf by adding the
<eviction-policy>tag under<cache-settings>:
<cache-settings ...>
<eviction-policy enabled="True" default-priority="normal" policy="priority" eviction-ratio="5%"/>
</cache-settings>
- Once changes are made, start the cache and restart NCache service.
Warning
eviction-ratio=5% is equal to 5% of total cache size. Eviction is not recommended in case of sessions.
See Also
General Cache Settings
Cache Cluster Settings
Error Logging
MapReduce