my ditto.
i'd sugest a one-shot swich, make full test on your new memached api wrapper
before that of coz. with a consistent hashing algo integrated,
pecl/memcached brings much better experience along.
i've tried to make a switch of same kind on 100+GB cache data months ago. no
worry, take it
The syntax differences don't lend themselves to being swapped out that
easily. Unless you are going to do a full code roll out to one set of
servers and not another, I don't think this is too easy.
They have different compression settings and I am not sure if they set
the same flag when
Fortunately, way back when we started using memcache I wrote a wrapper
for it to handle some of the more tedious stuff for me automatically.
All our code uses that wrapper class, so I just had to change the one
class to swap out extensions. :)
Unfortunately in our testing we are seeing some
hey jay,
we both are sailing in same boat!! I am in process of shifting from
pecl/memcache to pecl/memcached too. I have done some testing
yesterday itself, and have some feedback which might help you.
First of all, look very seriously and carefully which hashing policy
you were using(with
Hi all,
We're in the process of switching from the pecl memcache extension to
the pecl memcached extension, but we would like to start out by doing
a very limited rollout of the memcached extension so we can compare
performance and make sure everything is working as expected.
The documentation
