Hi Max. It's certainly not a "bad" idea per se, but it will probably take some amount of work to move all of this data. If you haven't already, please see the documentation on the bulk loader tool -- it's currently only available in Python, but you can still use it with your Java apps. It's a much better solution than setting a script to import all of your data in 30-second increments.
http://code.google.com/appengine/docs/python/tools/uploadingdata.html As leszek's link points out, applications with billing enabled can handle up to 500 requests per second by default, and this can be configured higher if your traffic warrants an increase. - Jason On Thu, Oct 15, 2009 at 12:01 AM, Max <max.seven....@gmail.com> wrote: > > I thought AppEngine is designed to scale. > But recently I heard that AppEngine does not scale. > > Someone benchmarked AppEngine with ab but AppEngine stopped to handle > requests after certain level of load. It seems that only one server > instance handle requests for 1 user. > > If I will switch to paid account will it scale in case when load > jumps? > > I though AppEngine is good choice for sites that may get high traffic. > > > ---- > > > 2. We had plans to move one of our databases (6~10 GB) to AppEngine > and access it throw REST. Is it a good idea? > > > > > Thanks, Max > > > --~--~---------~--~----~------------~-------~--~----~ 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-java@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 -~----------~----~----~----~------~----~------~--~---
