Hi Mark, No, write latency won't depend on the number of entities in the entity group - only on the rate of writes to the group.
-Nick Johnson On Thu, Jun 24, 2010 at 5:12 AM, Mark <[email protected]> wrote: > Hi, > > I've created two simple classes which I want to use in an entity > group: > > class User { > int numReports; > } > > class Report { > } > > the User object will always be the parent, Report instances are part > of a User's entity group. There can be many Report objects per User: > > User > |--- Report > > when I save a Report instance, I want to increment the 'numReports' > counter in the User object, in a transaction. This arrangement works > fine. > > But as the # of Report instances increase, does app engine have to > lock all other Report instances in the same entity group before > performing the transaction? I'm worried that performance will degrade > as the # of Report objects per User increases. > > 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]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 -- 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.
