In summary: Is it a bad idea to have one has an ancestor with many hundreds of children, and a high rate of child write updates.
I am not clear whether there are potential performance issues when using an ancestor structure where the one ancestor has many hundreds of children. I have a setup where a Project Kind has up to a thousand Task Kinds. The Task has a few dozen serialized activities that are checked out by users. As users complete each activity the Task gets updated, so there will be many thousands of Task updates. These may be clustered at times yielding a fairly high rate of transactions per minute I have a couple of Task composite indices right now supporting ancillary Project logic. I could get rid of these, and use ancestor queries, but am worried about those Task updates which for various reasons need to be fairly quick -- which I know is already a problem given the composite indices. Thanks in advance, stevep -- 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.
