Oops, missed the second reference:
[2] Section "Tips for using entity groups: " in
http://code.google.com/appengine/docs/python/datastore/keysandentitygroups.html
On Jan 19, 9:10 am, Tony Arkles wrote:
> Hi everyone!
>
> In a thread [1], and in the documentation [2], it says that setting
> ance
> The measured "ms-cpu" in the request logs comes out WAY smaller for
> the "ANCESTOR IS" query (roughly 3,000ms-cpu vs. 30,000 ms-cpu for
> 1,000 entities, and roughly this same ratio for smaller queries)
>
> Does anyone have any thoughts on this? Did I mess something up, or is
> there something
On Jan 19, 5:42 pm, Alexander Kojevnikov
wrote:
> From your second link:
>
> All entities in a group are stored in the same datastore node.
>
> I guess this means that entities from the same group are stored close
> to each other. When your query uses "ANCESTOR IS", the query engine
> can tak
On Jan 19, 7:10 am, Tony Arkles wrote:
>
> In a thread [1], and in the documentation [2], it says that setting
> ancestors doesn't affect performance, but I'm not sure that this is
> the case.
...
> The measured "ms-cpu" in the request logs comes out WAY smaller for
> the "ANCESTOR IS" query (rou
Thanks for the excellent reply Ryan!
On Jan 20, 3:54 pm, ryan wrote:
> On Jan 19, 7:10 am, TonyArkles wrote:
>
>
>
> > In a thread [1], and in the documentation [2], it says that setting
> > ancestors doesn't affect performance, but I'm not sure that this is
> > the case.
> ...
> > The measure
