Hi Paul, The overall execution time has been increased, but the limits on datastore queries have not. Use cursors and a loop.
Robert On Tue, Dec 14, 2010 at 16:42, Paul Bakker <paul.bakker...@gmail.com> wrote: > Hi Ikai, > It's mostly CPU time that it's using now just generating the test data. The > costs are lower than I expected though so no problem (and interesting to > note in the article). > I can't find any up to date information about the datastore timeout limits. > In 1.4 the background task timeout is 10 minutes, but long before that I get > a datastore timeout for a select all query with a dataset of a few million > rows. I know you shouldn't normally do this, but it's just to test and get > some numbers. Any idea about this? > Paul > On Mon, Dec 13, 2010 at 7:28 PM, Ikai Lan (Google) > <ikai.l+gro...@google.com> wrote: >> >> Hi Paul, >> You can enable billing for this. I doubt you'll end up paying a lot for >> it. Storage charges are based on snapshots and averaged for the month. >> Good luck! >> >> -- >> Ikai Lan >> Developer Programs Engineer, Google App Engine >> Blogger: http://googleappengine.blogspot.com >> Reddit: http://www.reddit.com/r/appengine >> Twitter: http://twitter.com/app_engine >> >> >> On Mon, Dec 13, 2010 at 4:54 AM, Paul Bakker <paul.bakker...@gmail.com> >> wrote: >>> >>> Hi Ikai, >>> Glad you like it. The article gets quite some hits so it seems there's a >>> lot of interest in this topic. I got some questions relating large volumes >>> of data. I'm working on another article that goes into the details of this. >>> To get some real numbers I need to run some benchmarks with larger amounts >>> of data (max 10 million rows), but I run into free quota limits. Is there >>> any way this limit could be stretched for a few days so I can finish the >>> article without having to pay a lot for it? I'm trying to advocate the use >>> of GAE after all :-) >>> My app id is gae-benchmarks. >>> Great work on the latest releases (most specifically no more 1000 row >>> limit in 1.3.1 and always on in 1.4). Takes away a lot of the reasons why >>> not to use GAE! >>> >>> -- >>> 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-appeng...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> google-appengine+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/google-appengine?hl=en. >> >> -- >> 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-appeng...@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. > > -- > 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-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- 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-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
