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 <t.ark...@gmail.com> wrote: > Hi everyone! > > 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. > > I set up two queries, one using "WHERE locationKey = :1" (locationKey > is a db.StringProperty), and one using "WHERE ANCESTOR IS :1" (the > ancestor is an entity created based on the locationKey). > > 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 from the documentation, or is it something else > entirely? > > Cheers > Tony > > [1]http://groups.google.com/group/google-appengine/browse_thread/thread/... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
