thanks ryan, As because it is generating proper uuid's before put(), I thought it could be an RPC call, we use batch put and get for datastore and the performance is impressive compared to individual put()
On Jan 29, 10:48 pm, ryan <[email protected]> wrote: > On Jan 29, 12:48 am, vivek <[email protected]> wrote: > > > If I use the above method for assigning the key_name, will it make a > > RPC call every time? > > happily, neither instantiating an Expando/Model subclass (ie running > the constructor) nor setting the _key_name attribute in memory will > make an RPC call. only put(), get*(), delete(), run_in_transaction(), > and queries make RPC calls. so, if you're just trying to avoid > unnecessary RPC calls, you can still go ahead and provide key_name in > the constructor. > > 200 entities is a lot to insert in a single HTTP request, but if > they're not too big and don't have too many properties, it may be > doable. you'll definitely want to pass them all into a single put() > call, instead of calling put() once per entity, so that the datastore > can handle them as a batch. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
