[wp-hackers] Memcached backend for the Object Cache
davebytes at comcast.net
Mon Dec 19 21:52:52 GMT 2005
Public-available servers won't really help -- you're not going over the open
internet to memcache...
Yes, this seems like only truly useful to:
- dedicated-hosting-box hosted sites
- larger WP rollouts (Wordpress.com, WPMU, smart hosts...) who want to trade
off physical memory to reduce database and hard disk hits.
Don't get me wrong.. I think it's a cool addition, and a few of the big WP
sites will find it immensely useful at reducing loads, but for the other 95%
of folks this is just something to dream about. ;)
The problem is getting >shared< hosts to learn and adopt technical
approaches that would reduce the load across their server farms. :)
Reducing disk load (well, and cpu) is a good piece... especially as it
reduces SQL hits as well. Can we get DreamHost to try it? ;)
----- Original Message -----
From: Aaron Brazell
To: wp-hackers at lists.automattic.com
Sent: Monday, December 19, 2005 4:27 PM
Subject: Re: [wp-hackers] Memcached backend for the Object Cache
Interesting but potentially useless to most bloggers who don't have access
to other servers... unless 127.0.0.1 can be used or if there will be
publically available servers for such purposes.
On 12/19/05, Ryan Boren <ryan at boren.nu> wrote:
On Mon, 2005-12-19 at 15:59 -0500, John Joseph Bachir wrote:
> On Mon, 19 Dec 2005, Ryan Boren wrote:
> > http://dev.wp-plugins.org/browser/memcached/trunk/
> This is exciting. Does it completely replace the filesystem based cache?
Yes. It caches to/from one or more memcached servers rather than using
the filesystem directly. You can define your servers and ports by
setting $memcached_servers in wp-config.php. By default, it looks for a
server on port 11211 on the local host.
Example server config:
$memcached_servers = array('192.168.1.1:11211 ', '192.168.1.2:11211');
More information about the wp-hackers