Our posts crossed paths in the ether. I don't think you should do 'get(key)' per request on the front end; rather, you should collect the keys and send them to the back end for use in a single batch get() call. It still might not completely suit your needs, but it would be much closer.
On Wednesday, August 1, 2012 2:24:10 PM UTC-4, Richard wrote: > > Ok, based on Takashi's suggestion, I now do the following: > > new_user_score = Score() > new_user_score.member = thing > new_user_score.put() > > # next part is new based on Takashi's suggestion > k = new_user_score.key() > db.get(k) > > WOW... I mean... HOLY CRIPES! Time to process each request went from > ~150msec to 4.5-7 SECONDS. > > This means I effectively need a one instance PER REQUEST. > > > On Wednesday, August 1, 2012 2:01:43 PM UTC-4, Richard wrote: >> >> Yep... got that. However, a query() will still return stale data between >> the put() and the (internal) commit(). Which is where I believe I am >> sitting... >> >> > -- 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/-/JWnUu8Em2EMJ. 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.
