Revisions to Magento session storage: Redis vs. Memcached

Question Protected by Amit Bera♦

occurred Apr 27, 2015 at 19:54

Tweeted twitter.com/#!/StackMagento/status/584358360327262208

occurred Apr 4, 2015 at 14:14

Rollback to Revision 2

Source Link

edited Apr 3, 2015 at 10:35

7ochem

7.6k
14
52
80

I'm running a Magento EE 1.12.2 (equally in CE 1.7.2) where we have Redis for caching (Cm_Cache extension, Redis v 2.2.12), but we use Memcache for session storage.

Redis is not supported out of the box on these Magento versions. So my concern here is:

Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement? Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement?
Isn't Memcache just as good or maybe even better? Isn't Memcache just as good or maybe even better?

In this project we have large session files as we need to store third-party XML files into the session, so optimizing session read and writes can have a considerable impact.

From local.xml:

<session_save><![CDATA[memcache]]></session_save>

And:

<cache>
    <backend>Cm_Cache_Backend_Redis</backend>
    [...]
</cache>

I'm running a Magento EE 1.12.2 (equally in CE 1.7.2) where we have Redis for caching (Cm_Cache extension, Redis v 2.2.12), but we use Memcache for session storage.

Redis is not supported out of the box on these Magento versions. So my concern here is:

Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement?
Isn't Memcache just as good or maybe even better?

In this project we have large session files as we need to store third-party XML files into the session, so optimizing session read and writes can have a considerable impact.

From local.xml:

<session_save><![CDATA[memcache]]></session_save>

And:

<cache>
    <backend>Cm_Cache_Backend_Redis</backend>
    [...]
</cache>

I'm running a Magento EE 1.12.2 (equally in CE 1.7.2) where we have Redis for caching (Cm_Cache extension, Redis v 2.2.12), but we use Memcache for session storage.

Redis is not supported out of the box on these Magento versions. So my concern here is:

Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement?
Isn't Memcache just as good or maybe even better?

In this project we have large session files as we need to store third-party XML files into the session, so optimizing session read and writes can have a considerable impact.

From local.xml:

<session_save><![CDATA[memcache]]></session_save>

And:

<cache>
    <backend>Cm_Cache_Backend_Redis</backend>
    [...]
</cache>

Rollback to Revision 3

Source Link

edited Apr 3, 2015 at 10:34

7ochem

7.6k
14
52
80

I'm running a Magento EE 1.12.2 (equally in CE 1.7.2) where we have Redis for caching (Cm_Cache extension, Redis v 2.2.12), but we use Memcache for session storage.

Redis is not supported out of the box on these Magento versions. So my concern here is:

Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement?Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement?
Isn't Memcache just as good or maybe even better?Isn't Memcache just as good or maybe even better?

In this project we have large session files as we need to store third-party XML files into the session, so optimizing session read and writes can have a considerable impact.

From local.xml:

<session_save><![CDATA[memcache]]></session_save>

And:

<cache>
    <backend>Cm_Cache_Backend_Redis</backend>
    [...]
</cache>

I'm running a Magento EE 1.12.2 (equally in CE 1.7.2) where we have Redis for caching (Cm_Cache extension, Redis v 2.2.12), but we use Memcache for session storage.

Redis is not supported out of the box on these Magento versions. So my concern here is:

Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement?
Isn't Memcache just as good or maybe even better?

In this project we have large session files as we need to store third-party XML files into the session, so optimizing session read and writes can have a considerable impact.

From local.xml:

<session_save><![CDATA[memcache]]></session_save>

And:

<cache>
    <backend>Cm_Cache_Backend_Redis</backend>
    [...]
</cache>

I'm running a Magento EE 1.12.2 (equally in CE 1.7.2) where we have Redis for caching (Cm_Cache extension, Redis v 2.2.12), but we use Memcache for session storage.

Redis is not supported out of the box on these Magento versions. So my concern here is:

Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement?
Isn't Memcache just as good or maybe even better?

In this project we have large session files as we need to store third-party XML files into the session, so optimizing session read and writes can have a considerable impact.

From local.xml:

<session_save><![CDATA[memcache]]></session_save>

And:

<cache>
    <backend>Cm_Cache_Backend_Redis</backend>
    [...]
</cache>

Removed backticks in listing which resulted in text to be displayed as 'code' (preformatted)

Source Link

edited Apr 3, 2015 at 10:34

7ochem

7.6k
14
52
80

I'm running a Magento EE 1.12.2 (equally in CE 1.7.2) where we have Redis for caching (Cm_Cache extension, Redis v 2.2.12), but we use Memcache for session storage.

Redis is not supported out of the box on these Magento versions. So my concern here is:

Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement? Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement?
Isn't Memcache just as good or maybe even better? Isn't Memcache just as good or maybe even better?

In this project we have large session files as we need to store third-party XML files into the session, so optimizing session read and writes can have a considerable impact.

From local.xml:

<session_save><![CDATA[memcache]]></session_save>

And:

<cache>
    <backend>Cm_Cache_Backend_Redis</backend>
    [...]
</cache>

I'm running a Magento EE 1.12.2 (equally in CE 1.7.2) where we have Redis for caching (Cm_Cache extension, Redis v 2.2.12), but we use Memcache for session storage.

Redis is not supported out of the box on these Magento versions. So my concern here is:

Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement?
Isn't Memcache just as good or maybe even better?

In this project we have large session files as we need to store third-party XML files into the session, so optimizing session read and writes can have a considerable impact.

From local.xml:

<session_save><![CDATA[memcache]]></session_save>

And:

<cache>
    <backend>Cm_Cache_Backend_Redis</backend>
    [...]
</cache>

I'm running a Magento EE 1.12.2 (equally in CE 1.7.2) where we have Redis for caching (Cm_Cache extension, Redis v 2.2.12), but we use Memcache for session storage.

Redis is not supported out of the box on these Magento versions. So my concern here is:

Is it worth the hassle to get session storage into Redis in terms of effort vs. speed improvement?
Isn't Memcache just as good or maybe even better?

In this project we have large session files as we need to store third-party XML files into the session, so optimizing session read and writes can have a considerable impact.

From local.xml:

<session_save><![CDATA[memcache]]></session_save>

And:

<cache>
    <backend>Cm_Cache_Backend_Redis</backend>
    [...]
</cache>

added 4 characters in body

Source Link

edited Apr 1, 2015 at 20:44

Amit Bera ♦

77.7k
20
124
239

Loading

added 177 characters in body

Source Link

edited Mar 20, 2015 at 14:20

7ochem

7.6k
14
52
80

Loading

Source Link

asked Mar 20, 2015 at 14:11

7ochem

7.6k
14
52
80

Loading

Stack Exchange Network

Return to Question