Hi, If i had to that, I would:
a) test the classical all-at-once fetch for the 15000 entities b) Then, if too long, I would try to break up the task and make it faster via Task. Tasks will provide you with parallel execution so you may get much faster. I would organize each subquery (as run asby a task) per entity-group (supposing that your entities are grouped as GAE permits it) so that 1 subquery goes to a single datastore server to avoid concurrency race in data fetching. This separation will also leverage the scalability / performances offered by App Engine. Of course, you will need to re-synchronize the subqueries at the end of all tasks to put all results back together. So, all of this would represent quite some coding. As I didn't try yet personally (it's only my thoughts), it's interesting to see if other members of this forum have something simpler to propose. regards didier On Dec 6, 11:36 am, sagar misal <sagar1982mi...@gmail.com> wrote: > I have gone through many articles declaring 1000 limit for single > query has been removed but still i don't want to stuck into query > fetch and deadline exceptions so can you please suggest me the best > way to query and search through around 15000 objects and sometimes > fetching all objects at a go.Right now am looking into Cursors,are > Cursors helpful in such cases? > Thank you. > Sagar Misal. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
