Memcache API versus Cache Router

Cache Router supports memcache clustering.

They are two different modules with different goals. Memcache module is very narrow in focus while Cache Router attempts to give flexibility to multiple cache types. Cache Router is also much newer and only in beta release at this point.

@slantview : would you mind adding a little more detail to the 'different goals' of each.

If I wanted to reduce load on my MySQL server via a server running memcached, what are the benefits of running the module 'Memcache API' versus the module 'Cache Router'?

The main difference is cacherouter uses different backends against memcache is memcache-only!

Another difference is that "Memcache API and Integration" seems to offer "a UI for memcache" and it "provides stats"; since I haven't yet installed this module, I can't vouch for this.

The "Cache Router" module advertises great looking stats, but had them removed a while ago; also, Cache Router doesn't offer any kind of administrative interface - so from within Drupal you will never know if the "Cache Router" module is configured properly, is operating well or is operating at all.

Greetings, -asb

That is not true. The stats have not been removed, the stats have never been fully realized yet. It is a feature that is in the DRUPAL-6--1 branch, but has not been released yet. The stats only really work for memcache and for APC currently. As soon as I have time to finish them and session handling, I will release a 1.0 release of Cache Router. I was hoping to have this done by Drupalcon, but it is looking like that is not going to happen as it is a week away now.

Subscribing.