Comments for Colin Mollenhour's Technical Blog http://colin.mollenhour.com Just another WordPress weblog Fri, 30 Dec 2011 22:08:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Benchmarking Zend_Cache backends for Magento by Colin Mollenhour http://colin.mollenhour.com/2011/10/03/benchmarking-zend_cache-backends-for-magento/comment-page-1/#comment-104 Colin Mollenhour Fri, 30 Dec 2011 22:08:00 +0000 http://colin.mollenhour.com/?p=144#comment-104 Hi Sanjay, this sounds like an issue with the driver and corrupt cache records. Are you using the phpredis (compiled) mode or the standalone mode? Please open an issue on the github project to continue discussion. -Thanks Hi Sanjay, this sounds like an issue with the driver and corrupt cache records. Are
you using the phpredis (compiled) mode or the standalone mode? Please open an issue on the github project to continue discussion. -Thanks

]]> Comment on Benchmarking Zend_Cache backends for Magento by Sanjay http://colin.mollenhour.com/2011/10/03/benchmarking-zend_cache-backends-for-magento/comment-page-1/#comment-103 Sanjay Fri, 30 Dec 2011 18:04:00 +0000 http://colin.mollenhour.com/?p=144#comment-103 Hi Colin, a little bit of background first - our Magento installation is split into Admin and Frontend being on different servers. We installed your tool on the frontend and it works really good. The redis server had been setup on the frontend server, we then configured the Admin to talk to frontend Redis but when we access the admin url, we get the error "invalid server response: e_1>0Alt_Image", is there any direction you can recommend for solving this? Cheers Sanjay   Hi Colin, a little bit of background first – our Magento installation is split into Admin and Frontend being on different servers. We installed your tool on the frontend and it works really good. The redis server had been setup on the frontend server, we then configured the Admin to talk to frontend Redis but when we access the admin url, we get the error “invalid server response: e_1>0Alt_Image”, is there any direction you can recommend for solving this?

Cheers
Sanjay  

]]> Comment on Benchmarking Zend_Cache backends for Magento by Anonymous http://colin.mollenhour.com/2011/10/03/benchmarking-zend_cache-backends-for-magento/comment-page-1/#comment-101 Anonymous Wed, 12 Oct 2011 00:18:00 +0000 http://colin.mollenhour.com/?p=144#comment-101 Hi Colin, it looks like a promising tool, thanks for sharing! I'm really looking forward to your post about Redis as I want to convince my customers to switch over from memcache. Keep up the good work.  Hi Colin, it looks like a promising tool, thanks for sharing! I’m really looking forward to your post about Redis as I want to convince my customers to switch over from memcache. Keep up the good work. 

]]> Comment on Benchmarking Zend_Cache backends for Magento by Colin Mollenhour http://colin.mollenhour.com/2011/10/03/benchmarking-zend_cache-backends-for-magento/comment-page-1/#comment-100 Colin Mollenhour Mon, 10 Oct 2011 23:42:00 +0000 http://colin.mollenhour.com/?p=144#comment-100 Yes, absolutely. Yes, absolutely.

]]> Comment on Benchmarking Zend_Cache backends for Magento by Anonim http://colin.mollenhour.com/2011/10/03/benchmarking-zend_cache-backends-for-magento/comment-page-1/#comment-99 Anonim Sat, 08 Oct 2011 16:33:00 +0000 http://colin.mollenhour.com/?p=144#comment-99  Can your backend be used without magento?  Like normal Zend_Cache backends ?  Can your backend be used without magento?  Like normal Zend_Cache backends ?

]]> Comment on About by Colin Mollenhour http://colin.mollenhour.com/about/comment-page-1/#comment-96 Colin Mollenhour Sun, 02 Oct 2011 02:17:13 +0000 http://colin.mollenhour.com/wordpress/?page_id=2#comment-96 Hi Justin. If you don't want to check third-party code into your repo then you can just check in a list of extension keys (extensions.txt) then use a shell command to make sure they are installed:<br><br>@shell <br>cd $PROJECT; <br>mkdir -f .installed <br>for ext in `cat $MODULE/extensions.txt`; do <br>if [ ! -f .installed/$ext ]; then<br>./pear install $ext && touch .installed/$ext; <br>fi <br>done Hi Justin. If you don't want to check third-party code into your repo then you can just check in a list of extension keys (extensions.txt) then use a shell command to make sure they are installed:

@shell
cd $PROJECT;
mkdir -f .installed
for ext in `cat $MODULE/extensions.txt`; do
if [ ! -f .installed/$ext ]; then
./pear install $ext && touch .installed/$ext;
fi
done

]]> Comment on About by Colin Mollenhour http://colin.mollenhour.com/about/comment-page-1/#comment-97 Colin Mollenhour Sun, 02 Oct 2011 02:17:12 +0000 http://colin.mollenhour.com/wordpress/?page_id=2#comment-97 Hi Justin. If you don't want to check third-party code into your repo then you can just check in a list of extension keys (extensions.txt) then use a shell command to make sure they are installed:<br><br>@shell <br>cd $PROJECT; <br>mkdir -f .installed <br>for ext in `cat $MODULE/extensions.txt`; do <br>if [ ! -f .installed/$ext ]; then<br>./pear install $ext && touch .installed/$ext; <br>fi <br>done Hi Justin. If you don't want to check third-party code into your repo then you can just check in a list of extension keys (extensions.txt) then use a shell command to make sure they are installed:

@shell
cd $PROJECT;
mkdir -f .installed
for ext in `cat $MODULE/extensions.txt`; do
if [ ! -f .installed/$ext ]; then
./pear install $ext && touch .installed/$ext;
fi
done

]]> Comment on About by Justin http://colin.mollenhour.com/about/comment-page-1/#comment-95 Justin Sun, 02 Oct 2011 01:55:49 +0000 http://colin.mollenhour.com/wordpress/?page_id=2#comment-95 Hi Collin, I'm looking forward to using Modman, which seems like a great utility.  I just have a question about best practices when it comes to 3rd party Magento extensions.  This must be a simple or obvious question as I haven't been able to find anyone addressing it online, but in a nutshell:  is there a best practice for dealing with 3rd party extensions when developing a Magento store, using source control and modman?  I'd rather not check 3rd party extensions in, so are they something that wouldn't even typically be handled by modman?  Just install the extensions I want by hand in my production, staging and dev environments individually?  Thanks for any thoughts you may have Hi Collin, I'm looking forward to using Modman, which seems like a great utility.  I just have a question about best practices when it comes to 3rd party Magento extensions.  This must be a simple or obvious question as I haven't been able to find anyone addressing it online, but in a nutshell:  is there a best practice for dealing with 3rd party extensions when developing a Magento store, using source control and modman?  I'd rather not check 3rd party extensions in, so are they something that wouldn't even typically be handled by modman?  Just install the extensions I want by hand in my production, staging and dev environments individually?  Thanks for any thoughts you may have

]]> Comment on About by Colin Mollenhour http://colin.mollenhour.com/about/comment-page-1/#comment-93 Colin Mollenhour Mon, 12 Sep 2011 07:57:04 +0000 http://colin.mollenhour.com/wordpress/?page_id=2#comment-93 <br><br><meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> <br><br>Maybe your comment didn't come through as expected, but I think<br>you're asking about configuring a prefix to avoid keyspace collisions?<br><br><br><br>The Redis cache does not use a configurable prefix. If you run more than one Magento installation on the same Redis server with the same database is then you will definitely have keyspace collisions. I<br>would recommend using a different Redis database for each Magento installation. This can be done with global/cache/backend_options/database. You could also run a separate instance of Redis on a different port, which would let you control<br>the amount of memory each installation can use.<br><br><br> <meta content=”text/html; charset=UTF-8″ http-equiv=”Content-Type”>

Maybe your comment didn't come through as expected, but I think
you're asking about configuring a prefix to avoid keyspace collisions?

The Redis cache does not use a configurable prefix. If you run more than one Magento installation on the same Redis server with the same database is then you will definitely have keyspace collisions. I
would recommend using a different Redis database for each Magento installation. This can be done with global/cache/backend_options/database. You could also run a separate instance of Redis on a different port, which would let you control
the amount of memory each installation can use.

]]> Comment on About by Colin Mollenhour http://colin.mollenhour.com/about/comment-page-1/#comment-94 Colin Mollenhour Mon, 12 Sep 2011 07:57:03 +0000 http://colin.mollenhour.com/wordpress/?page_id=2#comment-94 <br><br><meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> <br><br>Maybe your comment didn't come through as expected, but I think<br>you're asking about configuring a prefix to avoid keyspace collisions?<br><br><br><br>The Redis cache does not use a configurable prefix. If you run more than one Magento installation on the same Redis server with the same database is then you will definitely have keyspace collisions. I<br>would recommend using a different Redis database for each Magento installation. This can be done with global/cache/backend_options/database. You could also run a separate instance of Redis on a different port, which would let you control<br>the amount of memory each installation can use.<br><br><br> <meta content=”text/html; charset=UTF-8″ http-equiv=”Content-Type”>

Maybe your comment didn't come through as expected, but I think
you're asking about configuring a prefix to avoid keyspace collisions?

The Redis cache does not use a configurable prefix. If you run more than one Magento installation on the same Redis server with the same database is then you will definitely have keyspace collisions. I
would recommend using a different Redis database for each Magento installation. This can be done with global/cache/backend_options/database. You could also run a separate instance of Redis on a different port, which would let you control
the amount of memory each installation can use.

]]>