Hi Kenneth, There are a few good articles about writing scalable applications for google app engine: http://code.google.com/appengine/articles/scaling/overview.html
An example that might help: http://code.google.com/appengine/articles/sharding_counters.html - Wen On Aug 5, 7:51 am, Kenneth <[email protected]> wrote: > There's a lot of good information bubbling out about the pitfalls of moving > from from ms to hr, especially the problems with keys having your appid in > them. Apologies if this question has come up before. > > Like most others I suspect, 99% of my datastore objects don't have parents. > Since these are all in the same root entity group I'm now limited to 1-10 > writes per second to all of these objects if I don't reparent, according > tohttp://code.google.com/appengine/docs/python/datastore/hr/overview.ht... > > If my write rate does climb above 10/s I assume that I'm going to block? > > What is the strategy here? I can see making up something random as the > parent, but then I need that random thing to do a get_by_id since that's > what I do in most of my app, only passing the id to the user rather than the > whole key (which you are not supposed to pass to the user because it is a > security issue if you're using namespace). Am I screwed? > > This is of course leaving the whole issue of consistency aside, I'm ok with > that side of things, more or less. > > Thanks. -- 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.
