If you only need some of the properties for the query that needs 100+ results, you'll need to create a separate set of entities with just those properties, and query those. Similarly, if you want the query to return just the keys, you'll need entities containing the properties that are the subjects of query filters and the keys for the full entities.
100+ entities in a single request is a lot, especially with 40 properties on each entity. Smaller entities will get() faster, but you might also consider avoiding needing so many results at once. If you're hitting request timeouts and really need that much data, you could spread the requests across multiple requests using JavaScript. This won't reduce the total user time for the complete result set, but you could reduce perceived latency by displaying the first 20 results immediately while the remaining 80 are fetched. If you're trying to deliver the results all at once like in a downloadable spreadsheet, you'll have to get clever, maybe use memcache as a workspace and build it over multiple requests. -- Dan On Thu, Jan 8, 2009 at 1:07 PM, Tzakie <[email protected]> wrote: > > Looking at it more deeply every 20th one takes a long time. I assume > that's the data fetch. > > Still need a way to optimize... > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
