It's probably that expensive. There are many surprises when using the
datastore! I'd really like to get to grips with exactly what is
causing what performance issues because it still feels a bit
uncharted.
Possibilities:
Check if this speeds up if you call it a number of times in a row.
Your app m
I added items one at a time until I got to 30, then I did the empty,
so I'm pretty sure it wasn't a load request, this is normal.
Child entities have 4 fields with one being a list of Strings.
There is one index and it is 9% of the overall space.
Thanks,
Brian
On Thu, Dec 17, 2009 at 1:25 AM, Ri
Brian, in many cases it is changing the indexes that is expensive. Entities
are stored in a distributed key-value store, so a single write or delete is
cheap, but since we have to update the indexes synchronously, that could be
where you are paying the cost. For operations where you do not require
Thanks for the reply, the problem is the significant amount of cpu quota used.
Is there a way to optimize the index? I have just one.
Thanks,
Brian
Ikai L (Google) wrote:
Brian, in many cases it is changing the indexes that is expensive. Entities are
stored in a distributed key-value store,
