|
|
Posted by boots on 09/09/05 19:48
--- Marcus Bointon <marcus@synchromedia.co.uk> wrote:
> I've recently run into Frank Denis' http://sharedance.pureftpd.org/
> It strikes me as a near-perfect solution for Smarty config and
> caching on multi-server deployments - less overhead than SQL, less-
> error prone than shared files, faster than both - anyone tried it?
> I've used the same author's pureftpd server for ages and it couldn't
>
> be more solid...
Haven't seen this one before. I will have to test it eventually.
Usually I see people using or mentioning memcached
http://www.danga.com/memcached/ for these sorts of tasks. There is a
pecl package for memcached and the recently proposed Pear
System::Shared supports it (as well as other backends).
If all you want to do is cache configuration, and other relatively
static data, a typical solution, is to encode your data as php scripts
and use a more traditional PHP opcode accelerator. Though not
distributed, performance tends to be fantastic and as long as your
configuration and other common settings are not based on local states
determined by a slave, you can always push new updated scripts from a
master server on to each of the slave servers. I think this is simpler
because chances are, you already run a PHP accelerator (or should). In
fact, those distributed solutions seem best when you have a need to
share information that changes frequently and/or is otherwise expensive
to retrieve. In the case of Smarty, because it compiles everything to
PHP, it will take full advantadge of an opcode cache.
Just my 2c.
______________________________________________________
Click here to donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
Navigation:
[Reply to this message]
|