Posted by slantview on September 5, 2009 at 1:55pm
Spent A LOT of time over the past few days really getting into the bugs in Cache Router. This module is now entering the 1.0 release candidate world. It now "just works". For a lot of people it should be as easy as installing the module, adding the configs to settings.php and watching your site be 20-50% faster.
For bigger sites, this module will allow you to scale to great heights using memcache.
Here you go: 1.0-rc1 release - http://bit.ly/CMRRW Project page: http://drupal.org/project/cacherouter
Thanks to everyone who has helped out on this module. I finally had some time to dedicate to getting it to a much more stable place. I really hope we can have a 1.0 release out the door asap.
So please, use it, give feedback, profit!
-s
Comments
Congratulations, and thank you
Congratulations, and thank you for this great module. I've just updated the release data for Cache Router on the wiki page for comparison of performance modules.
eAccelerator?
Thank you for this module, when every $ for hosting counts. Is is 100% ok to run with eAccelerator?
drupal+me: jeweler portfolio
My tests show that it is 100%
My tests show that it is 100% working with eAccelerator. If you do find any problems, please let me know asap. Beware that eAccelerator versions 0.9.5 - 0.9.5.3 have a serious bug in them that allow retrieval of expired cache entries. I would recommend installing latest version from SVN if you want to use eAccelerator.
Collisions of class name?!
Why the main class name is Cache still?
As D7 have unified DrupalCacheInterface why not put it inside D5 and D6 with cacherouter?
Or this waits for 2.x branch?
Suppose it's much easy to maintain all classes are unified
Awesome!
Thanks for your work on this. I was able to remove the Cache Router fork code from Authcache.
http://httpremix.com
Several of us seeing severely
Several of us seeing severely degraded performance with cacherouter 1.0rc1 and using APC as cache. This is due to several hundred (or thousands) of error messages in the log file.It basically tried to unlink a file which does not exists. It is rather a cache key. Here is already opened issue but so far no luck. I was wondering if anyone of you could suggest solution.
See issue here http://drupal.org/node/588820
apc locking mechanism causing issues
In this release you added files as atomic locking mechanism for apc engine. This is causing more problems than the issue you are trying to resolve.
For anyone running into the
For anyone running into the same problem I did this morning using memcache not on localhost, here is the issue I created. In a nutshell the documentation says to set 'server' to your array of servers, yet the __construct for memcacheClass looks for 'servers', so if you set 'server' in the $conf array it will ignore it and roll over to localhost:11211.
HollyIT - Grab the Netbeans Drupal Development Tool at GitHub.