Bobcares

How to Set ElastiCache Redis Eviction Policy?

by | May 13, 2024

Read the article to know more on setting up of Eviction Policy in ElastiCache for Redis. Bobcares, as a part of our Server Management Service offers solutions to every query that comes our way.

Set ElastiCache Redis Eviction Policy

When the memory reaches the limit, Redis set up an automatic eviction policy, ElastiCache Redis Eviction Policy. This makes sure that we can write fresh data into the cache. The engine chooses which keys to evict in order to manage its memory when the cache memory exceeds. The eviction policy we choose will decide the key to select.

Let’s look into different ways in which we can set Eviction Policy.

Default Method

The Redis cluster’s volatile-lru eviction policy is set by default by Amazon ElastiCache for Redis. If this policy is chosen, keys with an expiration value specified that are the least recently used (LRU) are removed. The customizable maxmemory-policy parameter allows for the use of extra eviction policies.

Amazon ElastiCache for Redis provides a least frequently used (LFU) eviction policy for evicting keys in addition to the time-based LRU policy that is already in place. By keeping often used data in memory, the LFU method improves the cache hit ratio. It tracks the access counter for each object and evicts keys depending on the counter. After a time known as the decay period, the object decreases in value each time it is touched.

Manual Method

We can set different eviction policies in Redis:

1. noeviction: The default policy. If memory reaches the limit, Redis will return errors on write operations.
2. allkeys-lru: Evict the least recently used (LRU) keys out of all keys.
3. volatile-lru: Evict the least recently used (LRU) keys among keys that have an expire set.
4. allkeys-random: Remove random keys out of all keys.
5. volatile-random: Remove random keys among keys that have an expire set.
6. volatile-ttl: Remove keys with the closest expiration time among keys that have an expire set.

In ElastiCache Redis, we must edit the parameter group linked to the Redis instance in order to set up the policy. Here’s how to use the AWS CLI to do this:

elasticache redis eviction policy

With this code, the parameter group, my-group’s eviction policy is set to allkeys-lru. The eviction policy we select will have a substantial impact on the cache’s performance, so consider the use case carefully before making the decision.

For changes to take effect, we must apply the revised parameter group to the ElastiCache Redis cluster. There is no need to restart in order to take effect of this change.

[Need to know more? Click here to reach us.]

Conclusion

In conclusion, the article depicts two ways from our Support Team in which we can set up ElastiCache Redis eviction policy.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF