Skip to main content

Standard Configuration file for Redis

In my earlier post i have covered how to run multiple instances of redis also showed through a video how it can done.

In this post, I am going to cover best suitable redis (recently i come across this beautiful blog simplifying the concept of redis and its uses in real world) configuration file structure to have to minimize confusion to identify which ports belong to which cache.

for example if you are having several ports configured for redis, how you will determine which port is associated with which redis cache.So in our case i.e redis with Magento, we normally used 3 types of cache
  • Cache (magneto configuration files cache) 
  • Full Page Cache
  • Session Cache 






So, to avoid confusion among the ports and its associated cache, i would recommend to use following data in your redis configuration for each port respectively as shown.

  For Freelance Work & Queries Contact me by Email Id support@linuxforeveryone.com

1) Create a file with name redis-base.conf under /etc/ and put the below content in it.

vi /etc/redis-base.conf   

daemonize yes
timeout 0
tcp-keepalive 0
loglevel warning
databases 2
stop-writes-on-bgsave-error yes
rdbcompression no
maxmemory-policy volatile-lru
appendonly no  (disabling Append Only File) used for persistence
appendfsync everysec   OR always ?
no-appendfsync-on-rewrite no
slowlog-log-slower-than 10000
slowlog-max-len 1024
list-max-ziplist-entries 512
list-max-ziplist-value 64
set-max-intset-entries 512
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
activerehashing yes
slave-serve-stale-data yes
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
tcp-backlog 511
tcp-keepalive 0
repl-disable-tcp-nodelay no

above parameters will be common for all redis instances we are going to use for Cache, Full Page Cache and Session cache.

2)  Configuration file for Full Page cache







vi /etc/redis-fpc.conf


include /etc/redis/redis-base.conf
port 6381
pidfile /var/run/redis/redis-fpc.pid
logfile /var/log/redis/fpc.log
dir /var/lib/redis/fpc
maxmemory 1gb

3)  Configuration file for Session file

vi /etc/redis-ses.conf

include /etc/redis/redis-base.conf
port 6380
pidfile /var/run/redis/redis-ses.pid
logfile /var/log/redis/ses.log
dir /var/lib/redis/ses
maxmemory 1gb
save 900 1
save 300 10
save 60 10000

4) Configuration file for Cache

vi /etc/redis-obj.conf

include /etc/redis/redis-base.conf
port 6379
pidfile /var/run/redis/redis-obj.pid
logfile /var/log/redis/obj.log
dir /var/lib/redis/obj
maxmemory 3gb

We are including the base file /etc/redis/redis-base.conf within every configuration files as the base file is having common variables which would be require for cache/full_page_cache and session cache.

Let me know if you have any queries on above post, you can reach to me anytime.



Comments

  1. I love it whenever people come together and share thoughts.
    Great site, continue the good work!

    ReplyDelete
  2. Valuable info. Lucky me I found your web
    site by accident, and I am stunned why this coincidence didn't took place in advance!
    I bookmarked it.

    ReplyDelete

Post a Comment

Popular posts from this blog

Multiple instances of redis

In the last post I have covered how to install redis server on Centos/Rhel using rpm method and yum method and some troubleshooting skills. In this post i am going to cover how to install and configure redis to run with multiple ports.                                                                           But why we need more ports ? If you have read my earlier post , you already know that by default redis runs on single port 6379, which any one can use it for small website to cache the data. But for heavy website like magento we need to use additional ports along with 6379 to serve different cache from different ports. Like in Magento there is simple cache which is normally stored under /var/cache directory. Then there is Full Page Cache which is stored under /var/full_page_cache...

arbtd: Package isn't signed with proper key

  If you are System Admin and worked on linux machine or servers in your current job or in past. Chances are you might come across linux service abrtd, even if you have not worked on it. but might be through some other work. same thing happened to me, while I was doing my regular work of installing php packages on linux  servers , i came across this error for which spent couple of hours actually to resolve it. T he error was 

Resolving IP SKU Requirements When Adding Azure VMs to Load Balancers

When it comes to configuring Azure Virtual Machines (VMs) within a Load Balancer (LB) environment, there are essential requirements that need to be addressed to ensure optimal performance and reliability. One common challenge faced by Azure users is the necessity of configuring IP SKUs correctly. In this blog post, we'll explore this requirement, its importance, and provide a solution to address it effectively. Understanding the IP SKU Requirement   The IP SKU (Service Key Update) requirement plays a pivotal role in the proper functioning of your Azure infrastructure, particularly within the context of Load Balancers. Here's what you need to know : IP Should Be in Standard SKU When adding Azure VMs to a Load Balancer, it's highly recommended to utilize public IP addresses configured with the Standard SKU. The Standard SKU offers an array of advanced capabilities, including enhanced traffic management and load balancing options. By using Standard SKU, you ensure a higher deg...