More used items will remain in cache longer. So stuff that is infrequently used should naturally fall out.
If you've got entities that are frequently written to and seldom read, memcaching them will obviously have a lower value. Particularly if they are updated very often. Note that it may still make sense to memcache these in some cases, since it could still save a trip to the datastore. Robert On Thu, Feb 23, 2012 at 21:43, Thomas Wiradikusuma <[email protected]> wrote: > I haven't actually used it other than the one provided by Objectify :D > > I'm thinking of putting more (mostly rendered pages, recently accessed > items, lookups), but afraid memcache will become full and evicting more > important cache objects. > > What kind of misuse that you're talking? If I know I would avoid it. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/lQgcuPRdWgIJ. > > 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. -- 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.
