I am running memcache on an Amazon EC2 large instance (7.5GB RAM, 64 bit,
high i/o, etc). Is there a way to compute the optimum amount of storage
space and number of connections? I ask because I am right now using a
pulled-out-of-thin-air startup of:
/usr/bin/memcached -d -r -u nobody -m
I am running memcache on an Amazon EC2 large instance (7.5GB RAM, 64 bit,
high i/o, etc). Is there a way to compute the optimum amount of
storage space and number of connections? I ask because I am right now using
a pulled-out-of-thin-air startup of:
/usr/bin/memcached -d -r -u nobody -m
On Seg, 2011-11-21 at 11:07 -0800, jsd wrote:
Is this expected behavior? I would have hoped to just get a quick
connection refused, instead it gums up the connecting apache
processes for a long time, which is not good. Even better, I would
like to find some way to avoid running out of
Hi All,
My scenario needs me to retrieve multiple objects that have the same key.
Infact my scenario needs me to identify objects using multiple keys too,
but I can solve the multiple keys problem by adding one more entry to
memcached. So thats not my question. Is it possible to store multiple
Hi All,
My scenario needs me to retrieve multiple objects that have the same key.
Infact my scenario needs me to identify objects using multiple keys too,
but I can solve the multiple keys problem by adding one more entry to
memcached. So thats not my question. Is it possible to store
