hi guys! the conclusions here are largely correct. we intentionally keep interpreter state between requests in order to cache imported modules and global variables, as you mention. you're definitely encouraged to take advantage of this! more here:
http://code.google.com/appengine/docs/python/appcaching.html we don't provide any guarantees on how long those cached values will remain, or how often your requests will hit the same interpreter(s). it'd be pretty easy to measure yourself, though. i vaguely remember an earlier thread or two on this group that did just that. in general, you'll want to use this app caching for things that are expensive to compute, but not necessarily tied to any individual session or user. rendering templates is a common example. for session- or user-specific transient data, you'll generally want to use memcache instead. (of course, if you need the data to be persisted, use the datastore.) as for interpreter memory, i don't believe we've published any hard limits. the interpreter will raise a MemoryError if you run out of memory, though, so like with caching, you could try measuring it for your app yourself. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
