Hi, Memcache uses a shared pool of cache memory across applications, and at any given time the amount of memory free in the pool may vary. Memcache resources are managed so that we can maintain the highest cache hitrate possible, which ensures your application is running as efficiently as possible.
For an application with appreciable traffic, you can expect 100MB of Memcache resources, increasing proportionally as your app gets larger. However, there are no guarantees that any entry can be found in your cache at any given time. It's important to write your application robustly so that when an entry is not found in the cache, you retrieve the resource elsewhere. -Marzia On Tue, Oct 28, 2008 at 8:57 AM, pr3d4t0r <[EMAIL PROTECTED]> wrote: > > Greetings. > > Is the cache exhaustion policy for Memcache defined somewhere? The > documentation indicates that data are evicted due to memory exhaustion > in the cache, but gives no specific volumes about how that works. Is > the memory limit documented anywhere, or can you provide an insight? > > Thanks in advance and have a great day, > > pr3d4t0r > http://teslatestament.com > http://istheserverup.net > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
