Why not store the user data in memcache and work with that if you can? Followed by a periodical push into the datastore. Have your list of users that need to be updated in a memcache key as well.
I am doing this with a forum I am kicking about, storing the thread text in a memcache key, and having a memcache key store a list of threads, when something changes it updates the keys. I also fire off a datastore write. When there is a miss on the key it pulls from the datastore, shoves back into memcache, and on to processing. *Brian Davenport* On Fri, Jul 15, 2011 at 09:19, Zippoxer <[email protected]> wrote: > But how will it help me? It will still take the same time. > I asked for a way to make the update process (which I described above) > quicker. > > -- > 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/-/SZ0bhx1As8MJ. > > 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.
