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.html where > 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.
