My app may display a lot of different output for a given page (customized per user amongst other things), and I'm wondering how best to use memcache.
My current scheme is to estimate that a given user's output might be useful for, say 10 minutes, after which time the user has probably gone away so there's no point caching it. It's not that the content is invalid after 10 minutes (I explicitly clear memcache if content becomes invalid). Rather, I'm trying to aid memcache in determining what it can get rid of. Is this a good idea, or am I interfering with memcache's algorithm? It may all depend on the exact details of the application, but I'm wondering if there any general advice on memcache usage. Thanks.
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
