Rather than using memcached as a global site cache (which it is not really designed to be), you might have more success actually using it the way it was intended.
Which means as an object cache inside your code. Otherwise you are just going to be doing a lot of effort to get a square peg to fit in a round hole. On Sun, May 3, 2009 at 12:14 AM, Les Mikesell <[email protected]> wrote: > > maciek wrote: > >> I like the idea with unique keys, but the problem is I'm loading data >> from memcached by nginx, so keys must be in format '$http_host >> $request_uri'. >> > > Don't these get the article number as a component so new ones take care of > themselves except perhaps for a posters home with the current list? Maybe > you can make the home page have an iframe so the current list always checks > the application - which can cache this at a component level. > > idea with re-caching data - I'm not caching all pages from all blogs, >> on only that one visited in last 10h >> > > If you put stuff in that nobody wants it will be discarded as the least > recently used when another item needs space - no need to do extra work to do > that explicitly. > > -- > Les Mikesell > [email protected] > > -- "Be excellent to each other"
