[TYPO3-core] FYI72: enhancements to memcached caching backend

[Karsten Dambekalns]

Hi.

On 04.12.2008, at 12:21, Dmitry Dulepov wrote:
> When using addServer, connections problems do not happen until  
> someone calls get() or set() or any other function. So exception  
> catching does not work. When those get/set/other are called, it is  
> too late to catch errors already (page processing is in progress!).  
> So I would prefer to connect to servers first and ensure that they  
> are available. It is more effective than the current approach.

Well, if a cache is not available that should always be recoverable  
(i.e. build the cached info again). Easier said then done, but still  
true.

> About the pool. Using memcached makes sense when it is local.  
> Network delays will kill any benefits of using memcached.

While a local memcached will be faster accessible than a networked  
one, even that can be a lot faster than no cache. You know of the  
memcached clusters running into terabytes of RAM for facebook and  
other websites of that scale?

We could use connect() if only one server is specified and addServer()  
in other cases, as locally more than one memcached only makes sense[1]  
if you need more RAM than one instance can handle (which should be  
rather rare).

Regards,
Karsten

[1] because failover to another memcached on the same machine is  
useless if that machine hangs, is rebooted, whatever.
-- 
Karsten Dambekalns
Gimme Five!
http://typo3.org/gimmefive


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 304 bytes
Desc: This is a digitally signed message part
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20081204/166e0c5f/attachment.pgp