Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 71 by jc.redoutey: Statistics not updated when flush is issued in
binary mode
http://code.google.com/p/memcached/issues/detail?id=71
What steps will reproduce the problem?
1. Start memcached
2. Issue a flush in binary
i'm a newbie at php and i have to do something like that;
i have 5 rss content and must to send this texts to memcache...
firstly should i send content the mysql db and later mysql to memcache
and how?
Hi,
I just did a fresh build and install of libevent-1.4.12-stable and
memcached-1.4.0 on a 64bit centos
When I start memcached with
# /usr/local/bin/memcached -d -P /var/run/memcached.pid -u nobody -m
3 127.0.0.1 -p 11211
no pid file is created. It seems there was a bug about this awhile
Hi,
I'm using memcached together with Django to speed up the database
queries. One of my Django views (page) uses a query that takes over 20
sec. Normally this query hits the memcached cache and the data is
served almost instantly. The problem now is that if the cache expires,
the next person
Run a cron job that executes the query and updates the cache at an interval
shorter than the expiration time for the cached item.
On Wed, Aug 5, 2009 at 11:38 AM, Haes haes...@gmail.com wrote:
Hi,
I'm using memcached together with Django to speed up the database
queries. One of my Django
What happens when we release 1.4.1?
Your site really should be able to tolerate at least the brief loss of a
single memcached instance.
It's definitely good to update the cache asyncronously where possible, and
all of this stuff stuff (a lot is detailed in the FAQ too). I'd just
really like to
Or, to put it another way, memcached is *not a persistent data store nor
should it be treated as one. If your application will fail if memcached is
not running, odds are you are using memcached incorrectly.*
On Wed, Aug 5, 2009 at 1:36 PM, dormando dorma...@rydia.net wrote:
What happens when
Blah, missed this message before I responded :D But ya, totally
agreed here. If your site requires memcache in order to run, you are
in serious trouble. My general rule is no queries on a site should
take more then 0.2 seconds to run. Even with that, its a long time to
wait on a
most databases have a caching mechanism... if your page requires
processing before display, consider caching slow-load pages in a
database and write an algorithm to invalidate this cache only if their
supporting data changes... at this time of invalidation it should be
easy to re-cache the page
Yes, well... For most big sites I'd actually insist that it's okay if you
disappear from the internet if too many of your memcached instances go
away. Losing 10-50% might be enough to kill you and that's okay. Memcached
has been around long enough and integrated tight enough that it *is* a
Well, if you are talking about the MySQL query cache this is not a
safe alternative for a query that is taking a very long time to
execute. The query cache uses a global lock that can really cause
nightmares for your DB. This lock is used during every single query
against the table(s)
LarryK wrote:
Thanks, I did think of that too. I had changed the permissions to o+w
--
drwxr-xrwx 10 root root 4096 Aug 5 17:36 /var/run
Alternatively you could create the file s root and chown it to nobody
before starting memcached to avoid others to create files there...
Trond
On Thu, Aug 6, 2009 at 10:06 AM, Clint Webb webb.cl...@gmail.com wrote:
Actually, if you are using Memcache, then you will probably have better
performance if you disable the database cache.
Assuming you are using mysql, this page will help you disable it (which is
quite easy actually)
Hi,
here at nasza-klasa.pl, we were always a bit worried about the way
that memcached handles expired elements, which causes evictions of
unexpired entries even though there is a lot of garbage that could be
freed.
After introducing the patch below we managed to eliminate evictions
entirely
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?
Jay Paroline wrote:
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
I don't think we'll be able to take this patch due to changes we've
been making, however this is an *excellent* use case for our new
pluggable engine mechanism that's opening up for development soon.
On Aug 5, 10:01 pm, jakub.lopuszan...@nasza-klasa.pl
jakub.lopuszan...@nasza-klasa.pl wrote:
17 matches
Mail list logo
