We've run into this exact same issue and narrowed it down to the NIC,
but don't really know where to go from there. I'm going to look up
Dormando's suggestions but if anyone else has experience with this and
can point us in the right direction, it would be greatly appreciated.
Thanks,
Jay
On
One more shop here that uses gearmand for this!
:evicted_time 0
STAT items:40:outofmemory 0
STAT items:40:tailrepairs 0
END
On Apr 20, 12:40 am, Dustin dsalli...@gmail.com wrote:
On Apr 19, 9:04 pm, Jay Paroline boxmon...@gmail.com wrote:
Interestingly, I also recently noticed that we are using around 75% of
the allocated space on each of our
Interestingly, I also recently noticed that we are using around 75% of
the allocated space on each of our buckets even though they have been
up for 7.5 months. For us that's still more than enough space so I'm
not worried about it.
If it helps at all we're using an older version of memcached,
Ok, I think I wasn't clear enough in my question, so I wrote a simple
example.
?php
set_time_limit(0);
$m = new Memcached('pool');
$m-addServer('172.16.0.64', 11211);
$m-add('monkeys', '5');
while(1){
$m-get('monkeys');
sleep(5);
}
?
If 5 of these are running at the same time, I would
Currently we are (still) stuck using the PECL memcache extension, but
hopefully soon we will be moving to the libmemcached based PECL
memcached extension. I am trying to figure out if there is any way to
set it up to use persistent/shared connections.
Currently every apache/PHP process ends up
if they set
the same flag when sending compressed data. I have not had a reason to
look into it.
A simple test would tell you for sure. Just try it out on your test
systems and see how it works. Report back.
Brian.
http://brian.moonspot.net/
On 2/1/10 11:51 PM, Jay Paroline wrote
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
Hi guys,
I posted this to the libmemcached mailing list a while ago and didn't
get a response, but this list is a lot more active so I'm hoping
someone here will have answers for me. :)
I've taken some time to work on porting our code from using the PHP
PECL memcache extension to using the PECL
://brian.moonspot.net/
On 1/6/10 3:38 PM, Jay Paroline wrote:
Hi guys,
I posted this to the libmemcached mailing list a while ago and didn't
get a response, but this list is a lot more active so I'm hoping
someone here will have answers for me. :)
I've taken some time to work on porting our code
.
http://brian.moonspot.net/
On 1/6/10 3:45 PM, Jay Paroline wrote:
It looks like both/either. I added print statements in front of each,
and it doesn't get to the get. If I comment out the set, then it hangs
on the get.
Thanks,
Jay
On Jan 6, 4:43 pm, Brian Moonbr
^^the above works
What the heck is the difference?
Jay
On Jan 6, 5:15 pm, Trond Norbye trond.nor...@gmail.com wrote:
Try running your server from a console and add -vvv to the command
line. Does ti print out any progress?
On Wednesday, January 6, 2010, Jay Paroline boxmon...@gmail.com wrote
/bin
I made a sym link from /usr/bin to /usr/local/bin and restarted, and
it works like magic.
Jay
On Jan 6, 8:11 pm, Jay Paroline boxmon...@gmail.com wrote:
This is very odd. If I run it from the command line (with or without
vv) it works as expected. If it starts from init.d it doesn't work
I'm running this by you guys to make sure we're not trying something
completely insane. ;)
We already rely on memcached quite heavily to minimize load on our DB
with stunning success, but as a music streaming service, we also serve
up lots and lots of 5-6MB files, and right now we don't have a
for this purpose, e.g. squid set up as a reverse proxy.
On Mon, Nov 2, 2009 at 4:35 PM, Jay Paroline boxmon...@gmail.com wrote:
I'm running this by you guys to make sure we're not trying something
completely insane. ;)
We already rely on memcached quite heavily to minimize load on our DB
Just got this running on my box pointing at all our servers, so far
it's looking good! The only hiccup for me was that it expected the
yaml file to be in /etc and I was just editing it in place. Paying
attention to the error message made it pretty obvious what I did wrong
though.
Jay
dormando
Actually if anyone can provide hints about existing memcached
replication solutions, especially for php, that would make me very
happy. We have some keys that are very expensive to regenerate when
they fall out of memcached, so losing a bucket due to server failure,
maintenance, etc. is very
Hello,
We've been having some intermittent memcached connection issues and I
noticed that we are a couple of releases behind. Our current version
is 1.2.6.
Before I nag our admin about upgrading, is there any reason why it
might be more wise to go to 1.2.8 rather than make the leap to 1.4.0?
Another major disadvantage to the mysql query cache is that any time
data in a table is modified, all queries in the cache selecting or
joining across that table have to be invalidated. If you have a lot of
writes happening, your query cache will be virtually useless. At
Grooveshark we have
This might be an obvious question, but have you verified that
memcached is not going in to swap?
thengil wrote:
I've turned on GC logging and unfortunately it seems that the problem
is not ONLY due to full GCs. We've observed a full GC that took 1.2
seconds and that led to timeouts, but we've
We are doing slightly more writes than reads, and performance is still
quite acceptable.
Unfortunately I don't have any recent benchmarks, however.
We look at the expiration time as the answer to the question: how
stale can your data be and still be ok? for anything that is remotely
likely to fail to be invalidated. For us, 24 hours is what we use for
general system-state data and cached search results. Nobody really
cares or can tell if
Using a prefix can be handy. If you need to flush all queries from
memcache at the same time, while leaving other data in memcache, for
example, a simple way to do that is to simply change the prefix you
are using for queries. The key will be different, so all the old
entries are automatically no
Hi Clint,
This looks like a potentially incredibly useful tool for debugging. I
would be hesitant to commit to having that on our production servers,
but I would certainly run it on our dev servers.
Anyway, being able to see all keys by name is actually not all that
helpful for me because we
24 matches
Mail list logo
