No, there isn’t a direct easy way to do this. The FAQ addresses this, and provides a kind of workaround: Deleting by Namespace While memcached does not support any type of wildcard deleting or deletion by namespace (since there are not namespaces), there are some tricks that can be used to simulate this. They do … Read more
First I used mikewied’s solution, but then I bumped into the problem of auto starting the daemon. Another confusing thing in that solution is that it doesn’t use the config from etc. I was about to create my own start up scripts in /etc/init.d but then I looked into /etc/init.d/memcached file and saw this beautiful … Read more
I agree with most things @phihag has answered but I must clarify some things. Memcached stores data according to a key (phihag called it an id, not to be confused with database ids). Data can be of various sizes so you can store small bits (like 1 record pulled from the database) or you can … Read more
To see if it is running you could also try telnetting into the port: telnet localhost 11211 If this works you will see the following (telling you that the given port is open): Connected to localhost. Escape character is ‘^]’. Now if memcached IS running you can see some basic stats by issuing the given … Read more
You can set key expiration to a date, by supplying a Unix timestamp instead of a number of days. This date can be more than 30 days in the future: Expiration times are specified in unsigned integer seconds. They can be set from 0, meaning “never expire”, to 30 days (60*60*24*30). Any time higher than … Read more
Using root, try something like this: /etc/init.d/memcached restart
Varnish is in front of the webserver; it works as a reverse http proxy that caches. You can use both. Mostly write — Varnish will need to have affected pages purged. This will result in an overhead and little benefit for modified pages. Mostly read — Varnish will probably cover most of it. Similar read … Read more