Hi, Yes, for such a task you will have to go via the Task Queue: an interactive task of this size would for sure reach the allowed limits.
The way it works is : read an entity, do the updates, check the duration since start, if far from limit process another entity, if close to limit, reschedule a new task with next entity to be processed as starting point. Via the task queue, you will gain another advantage: parallelism, you can scan your data with more than 1 task and then complete the job much faster. Be careful about contention on the datastore though! (to avoid, you should split your key range in N chunks and affect a task to each chunk) regards didier On Aug 25, 7:31 am, Baz <[email protected]> wrote: > Hello, > > I have a non-user triggered process that queries the datastore for a dataset > of about 100k records, then loops through each record to update two other > entities in the datastore. What would be a good way to go about doing this? > I'm concerned about timing out and/or consuming more resources than I need > to. Task queue? > > Cheers. -- 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 [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-java?hl=en.
