search

colinmollenhour / Cm_Cache_Backend_Redis

A Zend_Cache backend for Redis with full support for tags (works great with Magento)
Other
389 stars 142 forks source link

Better divide cache and sessions #86

Closed michelem09 closed 9 years ago

michelem09 commented 9 years ago

Hi, I was experiencing some connection issues with my Magento, I had this setup: 3 web servers in load balancing with 1 storage server (NFS) and 1 Redis server to handle cache and sessions.

I noticed that with this setup I had a lot of errors like "Connection to Redis failed after 2 failures", so I tried to divide the load of sessions and cache in 2 different redis servers and it seems connection errors have gone away.

Is it possible there is a problem keeping both your modules (cache, sessions) connected to the same redis instance (of course with different db #)? Did you have same complaints in past?

csdougliss commented 9 years ago

Hi @michelem09

In a production environment I have Magento connecting to a cache instance on port 6379 and for sessions on port 6380 (so basically I have 2 redis instances running).

I do sometimes have issues with redis failure but it seems to have gone away

michelem09 commented 9 years ago

So you are saying the same, the connection issues could happen more if cache and sessions are on the same redis instance. I wanna try that too, now I tried with two completely different servers (one for cache, one for session), but I'd like to try with two redis instances on the same server.

x86fantini commented 9 years ago

we also run multiple instances of Redis on same server, with different ports (6379, 6380, 6381, etc..) in this way we have different config files and different memory allocation for each services and its working really fine

2015-02-12 10:38 GMT+01:00 Michele Marcucci notifications@github.com:

So you are saying the same, the connection issues could happen more if cache and sessions are on the same redis instance. I wanna try that too, now I tried with two completely different servers (one for cache, one for session), but I'd like to try with two redis instances on the same server.

— Reply to this email directly or view it on GitHub https://github.com/colinmollenhour/Cm_Cache_Backend_Redis/issues/86#issuecomment-74042442 .

michelem09 commented 9 years ago

Thanks for feedbacks. I did the change and I put every redis instances in the same server and I still have the same good performance. So I think it's definitely worth divide the load between several redis instances instead using the same for everything.

x86fantini commented 9 years ago

Redis is single thread. So multiples cores = multiple instances. Btw, always use db "0" with credis library since now you have moved each service in his own instances. We do the same and it's working like a charm

2015-02-12 13:03 GMT+01:00 Michele Marcucci notifications@github.com:

Thanks for feedbacks. I did the change and I put every redis instances in the same server and I still have the same good performance. So I think it's definitely worth divide the load between several redis instances instead using the same for everything.

— Reply to this email directly or view it on GitHub https://github.com/colinmollenhour/Cm_Cache_Backend_Redis/issues/86#issuecomment-74060438 .