On Fri, Aug 19, 2011 at 6:49 PM, Fred Sauer <fre...@google.com> wrote: >> >> If you don't want to give you eventual consistency, try this: >> >> my_members = db.get(my_keys, >> config=db.create_config(max_entity_groups_per_rpc=1)) > > Also, for reference, here's what this does: > > @ConfigOption > def max_entity_groups_per_rpc(value): > """The maximum number of entity groups that can be represented in one > rpc. > For a non-transactional operation that involves more entity groups than > the > maximum, the operation will be performed by executing multiple, > asynchronous > rpcs to the datastore, each of which has no more entity groups > represented > than the maximum. So, if a put() operation has 8 entity groups and the > maximum is 3, we will send 3 rpcs, 2 with 3 entity groups and 1 with 2 > entity groups. This is a performance optimization - in many cases > multiple, small, concurrent rpcs will finish faster than a single large > rpc. The optimal value for this property will be application-specific, > so > experimentation is encouraged. > """
It feels like you'd always want to set this to 1. What situations might make >1 perform better? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
