Hi Jay, Correct, memcache is global to your app. The same user's requests could go to any of your instances. So caching user datain local memory is probably not worth it.
Robert On Thu, Sep 8, 2011 at 21:51, jay <[email protected]> wrote: > Oh, I just read that memcache is constant across instances. > > On Sep 9, 12:43 pm, jay <[email protected]> wrote: >> Quick question, >> >> In my app users "do work" on some data. Every action they do I have to >> pull the data out of the datastore, unpickle it, do the transform, >> pickle it again and put it back in the datastore. >> >> Do today I'm doing some optimization where I'll look in the memcache >> first for the unpicked data. >> >> I was wondering if the user is sitting at their desk doing something >> every 5-10 seconds or so, and I have 5 or 6 instances running, are >> they likely to be hitting the same instance over and over, based on >> geography (or something else), or will they be making requests of a >> completely random one of my instances. >> >> Just wondering. >> >> Thanks in advance. > > -- > 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. > > -- 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.
