On Thu, Jan 8, 2009 at 3:35 PM, Tzakie <[email protected]> wrote:
> > Thanks very much for your time guys. > No problem, happy to help. > When you call: > CategoryRows = db.GqlQuery(QueryString) > It's fast. > > It's the loop where you try and access the returned entities that > is slow. Doesn't it follow that the CategoryRows has the keys in it > and the next() in the python loop is fetching them? every 20th > next() call is also takes extra time. Like it's fetching 20 at a > time from some place. Actually, db.GqlQuery() (and db.Query() and Model.all() and Model.gql()) only sets up the query, it does not execute it. The query is executed when you retrieve the results using q.fetch(), q.get(), or the iterator interface (for result in q: ...). We definitely hear your concerns about the desired scale of single operations, and we're always working to improve these numbers. But it's worth considering that App Engine is a scalable system intended to offer the same performance characteristics whether your data set has thousands of items or millions of items. To do that, it has to behave differently than a single-server relational database. Quite frankly, I can't think of a Google web app that displays 100 of anything all at once... -- Dan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
