{"id":1152,"date":"2018-12-11T02:00:50","date_gmt":"2018-12-11T04:00:50","guid":{"rendered":"https:\/\/magenteiro.com\/blog\/?p=1152"},"modified":"2018-11-22T04:56:47","modified_gmt":"2018-11-22T06:56:47","slug":"como-habilitar-e-configurar-o-redis-no-magento","status":"publish","type":"post","link":"https:\/\/www.magenteiro.com\/blog\/magento-1\/como-habilitar-e-configurar-o-redis-no-magento\/","title":{"rendered":"Como habilitar e configurar o Redis no Magento"},"content":{"rendered":"

Neste artigo veremos como habilitar o Redis no Magento 1<\/strong>. Caso esteja procurando como habilitar o Redis no Magento 2<\/a> consulte este link.<\/p>\n

O que \u00e9 Redis e como isso pode melhorar meu Magento?<\/h2>\n

O Redis \u00e9 um projeto open source que permite salvar dados estruturados em mem\u00f3ria (ram) usando um banco de dados de chave-valor.<\/p>\n

O Magento vem preparado para ser integrado com este tipo de mem\u00f3ria e permite salvar arquivos de cache e sess\u00e3o direto no Redis, ao inv\u00e9s de salvar em disco ou banco de dados.<\/p>\n

Como sabemos, o acesso \u00e0 mem\u00f3ria ram \u00e9 muito mais r\u00e1pido que o acesso aos arquivos em disco ou mesmo ao banco de dados mysql.<\/p>\n

Verificando disponibilidade<\/h2>\n

A maioria das hospedagens especializadas em Magento<\/a> fornecem Redis mesmo nos planos mais b\u00e1sicos.<\/p>\n

Uma forma simples de verificar se sua hospedagem possu\u00ed o Redis instalado \u00e9 logando no console (ssh<\/em>) e digitando redis-cli<\/code>.<\/p>\n

\nhttps:\/\/magenteiro.com\/blog\/wp-content\/uploads\/2018\/11\/redis-cli.mp4<\/a><\/video><\/div>\n

Configurando Magento 1 com Redis<\/h2>\n

O m\u00f3dulo respons\u00e1vel por salvar dados da session<\/em> no Redis \u00e9 o Cm_RedisSession<\/code>, nativo<\/strong> mesmo nas vers\u00f5es Open Source do Magento.<\/p>\n

Toda a configura\u00e7\u00e3o \u00e9 feita no arquivo app\/etc\/local.xml<\/code>. Por padr\u00e3o, a maioria dos servidores Redis s\u00e3o configurados na porta 6379,\u00a0 e isso facilita bastante nosso trabalho.<\/p>\n

Na pasta app\/etc<\/code> voc\u00ea encontra o arquivo local.xml.additional<\/code>que cont\u00e9m um exemplo de configura\u00e7\u00e3o Redis para cache comum, session e at\u00e9 full page cache, al\u00e9m de exemplos de configura\u00e7\u00e3o de memcached<\/em>.<\/p>\n

Cache com Redis no Magento 1<\/h3>\n

Para fazer com que o magento passe a salvar os arquivos de cache em mem\u00f3ria ram ao inv\u00e9s de salvar na pasta var\/cache, basta copiarmos o trecho abaixo no arquivo local.xml.additional<\/code> para o nosso app\/etc\/local.xml<\/code>.
\n

<config>\r\n    <global>\r\n        <!-- example of redis cache -->\r\n        <cache>\r\n            <backend>Cm_Cache_Backend_Redis<\/backend>\r\n            <backend_options>\r\n                <server>127.0.0.1<\/server>                               <!-- or absolute path to unix socket -->\r\n                <port>6379<\/port>\r\n                <persistent><\/persistent>                                <!-- Specify unique string to enable persistent connections. E.g.: sess-db0; bugs with phpredis and php-fpm are known: https:\/\/github.com\/nicolasff\/phpredis\/issues\/70 -->\r\n                <database>0<\/database>                                   <!-- Redis database number; protection against accidental data loss is improved by not sharing databases -->\r\n                <password><\/password>                                    <!-- Specify if your Redis server requires authentication -->\r\n                <force_standalone>0<\/force_standalone>                   <!-- 0 for phpredis, 1 for standalone PHP -->\r\n                <connect_retries>1<\/connect_retries>                     <!-- Reduces errors due to random connection failures; a value of 1 will not retry after the first failure -->\r\n                <read_timeout>10<\/read_timeout>                          <!-- Set read timeout duration; phpredis does not currently support setting read timeouts -->\r\n                <automatic_cleaning_factor>0<\/automatic_cleaning_factor> <!-- Disabled by default -->\r\n                <compress_data>1<\/compress_data>                         <!-- 0-9 for compression level, recommended: 0 or 1 -->\r\n                <compress_tags>1<\/compress_tags>                         <!-- 0-9 for compression level, recommended: 0 or 1 -->\r\n                <compress_threshold>20480<\/compress_threshold>           <!-- Strings below this size will not be compressed -->\r\n                <compression_lib>gzip<\/compression_lib>                  <!-- Support gzip, lzf, lz4 (https:\/\/github.com\/kjdev\/php-ext-lz4) or snappy (https:\/\/github.com\/goatherd\/php-snappy) -->\r\n                <use_lua>0<\/use_lua>                                     <!-- Set to 1 if Lua scripts should be used for some operations -->\r\n            <\/backend_options>\r\n        <\/cache>\r\n    <\/global>\r\n<\/config><\/pre><\/p>\n
Full Page cache com Redis no Magento 1<\/h3>\n
O mesmo vale para o full_page_cache.<\/em>
\n
<config>\r\n    <global>\r\n        <!-- example of redis Magento Enterprise FPC -->\r\n        <full_page_cache>\r\n            <backend>Cm_Cache_Backend_Redis<\/backend>\r\n            <backend_options>\r\n                <server>127.0.0.1<\/server>              <!-- or absolute path to unix socket -->\r\n                <port>6379<\/port>\r\n                <persistent><\/persistent>               <!-- Specify unique string to enable persistent connections. E.g.: sess-db0; bugs with phpredis and php-fpm are known: https:\/\/github.com\/nicolasff\/phpredis\/issues\/70 -->\r\n                <database>1<\/database>                  <!-- Redis database number; protection against accidental data loss is improved by not sharing databases -->\r\n                <password><\/password>                   <!-- Specify if your Redis server requires authentication -->\r\n                <force_standalone>0<\/force_standalone>  <!-- 0 for phpredis, 1 for standalone PHP -->\r\n                <connect_retries>1<\/connect_retries>    <!-- Reduces errors due to random connection failures -->\r\n                <lifetimelimit>57600<\/lifetimelimit>    <!-- 16 hours of lifetime for cache record -->\r\n                <compress_data>0<\/compress_data>        <!-- DISABLE compression for EE FPC since it already uses compression -->\r\n            <\/backend_options>\r\n        <\/full_page_cache>\r\n\r\n    <\/global>\r\n<\/config><\/pre>
\nLembre-se de ativar o Full Page Cache em Sistema->Configura\u00e7\u00e3o->Avan\u00e7ado->Sistema->External Full Page Cache Settings.<\/em><\/p>\n
\"Full<\/p>\n
Session com Redis<\/h3>\n
E para salvar os dados de sess\u00e3o em mem\u00f3ria:
\n
<config>\r\n    <global>\r\n        <!-- example of redis session storage -->\r\n        <session_save>db<\/session_save>\r\n        <redis_session>                                          <!-- All options seen here are the defaults -->\r\n            <host>127.0.0.1<\/host>                               <!-- Specify an absolute path if using a unix socket -->\r\n            <port>6379<\/port>\r\n            <password><\/password>                                <!-- Specify if your Redis server requires authentication -->\r\n            <timeout>2.5<\/timeout>                               <!-- This is the Redis connection timeout, not the locking timeout -->\r\n            <persistent><\/persistent>                            <!-- Specify unique string to enable persistent connections. E.g.: sess-db0; bugs with phpredis and php-fpm are known: https:\/\/github.com\/nicolasff\/phpredis\/issues\/70 -->\r\n            <db>0<\/db>                                           <!-- Redis database number; protection from accidental loss is improved by using a unique DB number for sessions -->\r\n            <compression_threshold>2048<\/compression_threshold>  <!-- Set to 0 to disable compression (recommended when suhosin.session.encrypt=on); known bug with strings over 64k: https:\/\/github.com\/colinmollenhour\/Cm_Cache_Backend_Redis\/issues\/18 -->\r\n            <compression_lib>gzip<\/compression_lib>              <!-- gzip, lzf, lz4 (https:\/\/github.com\/kjdev\/php-ext-lz4) or snappy (https:\/\/github.com\/goatherd\/php-snappy) -->\r\n            <log_level>1<\/log_level>                             <!-- 0 (emergency: system is unusable), 4 (warning; additional information, recommended), 5 (notice: normal but significant condition), 6 (info: informational messages), 7 (debug: the most information for development\/testing) -->\r\n            <max_concurrency>6<\/max_concurrency>                 <!-- maximum number of processes that can wait for a lock on one session; for large production clusters, set this to at least 10% of the number of PHP processes -->\r\n            <break_after_frontend>5<\/break_after_frontend>       <!-- seconds to wait for a session lock in the frontend; not as critical as admin -->\r\n            <break_after_adminhtml>30<\/break_after_adminhtml>\r\n            <first_lifetime>600<\/first_lifetime>                 <!-- Lifetime of session for non-bots on the first write. 0 to disable -->\r\n            <bot_first_lifetime>60<\/bot_first_lifetime>          <!-- Lifetime of session for bots on the first write. 0 to disable -->\r\n            <bot_lifetime>7200<\/bot_lifetime>                    <!-- Lifetime of session for bots on subsequent writes. 0 to disable -->\r\n            <disable_locking>0<\/disable_locking>                 <!-- Disable session locking entirely. -->\r\n            <min_lifetime>60<\/min_lifetime>                      <!-- Set the minimum session lifetime -->\r\n            <max_lifetime>2592000<\/max_lifetime>                 <!-- Set the maximum session lifetime -->\r\n        <\/redis_session>\r\n    <\/global>\r\n<\/config><\/pre>
\nLembre-se de remover ou comentar o n\u00f3 original <session_save><![CDATA[files]]><\/session_save><\/code>.<\/p>\n
 <\/p>\n
O que voc\u00ea precisa saber<\/h2>\n
Uma vez que o controle do cache passa a estar no Redis, nem tudo pode ser gerenciado via painel.<\/p>\n
Quando voc\u00ea quiser limpar todos os caches do Magento o painel de controle pode n\u00e3o ser suficiente.<\/p>\n
Como vimos acima, n\u00f3s configuramos 3 databases<\/em> diferentes atrav\u00e9s das diretivas <db><\/code> e <database><\/code> no nosso local.xml<\/code>.<\/p>\n
Com o comando flushdb<\/code> podemos limpar toda base selecionada, como vemos no exemplo abaixo:<\/p>\n