So, I changed the function to fetch instead of iterating over the results. I just did about 30 minutes of testing and I didn't have any errors in the logs. However, I don't think this proves that it's working better because I've had hours under load before where I haven't gotten the errors, and then all of a sudden I'll get dozens of errors in a row. I'll keep an eye on this new version and see how it goes.
That said, have others found that fetch is more efficient than using the iterator over the datastore results? If so, I'll stop using the iterators. (That couldn't be right, could it?) -Rob On Nov 21, 7:34 am, Rob <[EMAIL PROTECTED]> wrote: > > Do the timeouts still happen if you use fetch() when iterating over > > queries? > > > for curplayer in query.fetch(100): > > Thanks for writing. I can give that a try. I expected having to > fetch all of the players at the same time (even if there are only a > few) would initially take longer than finding one at a time with the > iterator, but I haven't actually tried that yet. If nothing else, > it'll help diagnose if the performance problem is localized to the > iterator in my app. > > Thanks for the suggestion. I'll write back later tonight after I've > given that a try. > > -Rob --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
