Re: [google-appengine] Architecture approaches for puts

2010-11-12 Thread Stephen Johnson
I apologize if this has been asked and answered in this thread. I tried looking through it but it is very long. From what I can tell you haven't answered what your latency is for these requests and I believe that is very important before you do all the work which is outlined below. From what I

Re: [google-appengine] Architecture approaches for puts

2010-11-10 Thread Eli Jones
How big is the average entity for this Model that you are putting to? (Are you just putting one entity at a time?) If you create a separate Model with the same properties but no indexes, how long and how much CPU does it use up on a put (in comparison to your fully indexed model)? Also, what do

[google-appengine] Architecture approaches for puts

2010-11-09 Thread stevep
I would like some feedback about pluses / minuses for handling new records. Currently I need to optimize how the client request handler processes new entity put()s. Several custom indices for the model are used, so puts run too close to the 1,000 ms limit (were running over the limit prior to Nov.

Re: [google-appengine] Architecture approaches for puts

2010-11-09 Thread Robert Kluin
Why not use allocate_ids to generate the ids? That might simplify the process a bit. http://code.google.com/appengine/docs/python/datastore/functions.html#allocate_ids I've been using a similar process for batch updates for quite some time. Works well for my case, but in my case there is not