Thanks Simon and Jeff. Feel bad that I missed this point, as I had read it before.
To summarize: A parent with many children comprises an group. Updates to a group are limited to one per second. If I were to use this ancestor setup, I would need to provide logic that would in effect batch a group's children updates, and apply them not more than once per second. stevep On Nov 23, 11:08 am, Jeff Schnitzer <[email protected]> wrote: > Just to clarify this slightly, you need to engineer for a throughput of one > write transaction per second per entity group. You can update lots of > entities in a single entity group per transaction. > > Jeff > > > > > > > > > > On Wed, Nov 23, 2011 at 12:44 PM, Simon Knott <[email protected]> wrote: > > If you only have a single parent, then you will be limited to the 1 write > > per second limit on individual entity groups (see bottom of > >http://code.google.com/appengine/docs/python/datastore/hr/overview.htmlwhere > > this is noted as a limitation of this kind of structure). > > > If you attempt many updates to the children, I'd expect to get a lot of > > concurrent-modification exceptions. > > > -- > > 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/-/HkDXRsugLd0J. > > > 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. > > -- > I am the 20% -- 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.
