In general the number of keys requested should not cause the query time to greatly increase, but it depends on the complexity of the query. A true "keys only" request should only cause us to traverse an index. Composite queries will require us to merge-join indexes, but, computationally, this should not take significantly more time to traverse. Most real world use cases will be more complex, unfortunately. If you have an example of a query that is not behaving in this matter, please post it to the list so we can try to figure out what's happening.
On Fri, Jan 8, 2010 at 3:32 PM, Derrick <[email protected]> wrote: > Does anyone have data on how API time spent varies on a given query as > you change the number of keys that you request for a "keys only" > query? Is asking for 50 keys approximately the same cost as 1 or 200 > or 500? > > -- > 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]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > > -- Ikai Lan Developer Programs Engineer, Google App Engine--
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.
