Nick, If we (I work with Gary) require fairly heavy requests which run for multiple seconds then it is not possible to get anywhere near 400 QPS. The math used on the docs page only applies to 75ms requests.
(1000 ms/second / 75 ms/request) * 30 = 400 requests/second so lets say each request takes 10 seconds (and ours, pulling data to EC2 for a heavy operation that we can't do on GAE could take that much since we have to process and update some XML before sending it) (1000 ms/second / 10000 ms/request) * 30 = 3 requests/second And that does not even take into account all the other traffic to our application, nor the fact that many users could be doing this same heavy operation at the same time. Our application will see spikes in this type of activity also. The docs also mention that CPU heavy apps incur penalties, which is vague and scary. Great effort is put into doing things in the most efficient way possible, but not everyones apps can do everything in 75ms. Most all of our service calls are under 250ms. We do have a little overhead from our framework which we are constantly working on improving. Our application is AMF service/object based which is inherently heavy compared to simple web requests. It limits the amount of memcache work we can do also, but we are also working on improving our use of that. We easily hit these boundaries during testing so I think we really need much higher simultaneous dynamic request limits for not only our production instance but our dev/qa instances so we can test and load them to some degree. Our QA team could easily bust this limit 20 times over. So, Nick Johnson... I ask your advice. We are running a company/product on GAE. We are more than happy to pay for quota/service/extra assistance in these matters. What do you suggest we do? I should also mention that I spoke with Brett Slatkin at PyCon and he is now at least semi-familiar with the scope of product we have developed. I have exchanged contact info with him but have not heard anything back from him yet. We would really appreciate contact or even a brief meeting at some point (in person or otherwise). Thanks, -Mike Wesner On Mar 1, 2010, at 7:40 AM, Nick Johnson (Google) wrote: > Hi Gary, > > Practically speaking, for an app that hasn't been given elevated permissions, > you should be able to have at least 30 concurrent requests - equating to > around 400 QPS if your app is fairly efficient. What problems are you running > into that lead you to conclude you're hitting a limit at 4 QPS, and that the > problem is at App Engine's end? > > -Nick Johnson > > On Sat, Feb 27, 2010 at 8:23 PM, Gary Orser <garyor...@gmail.com> wrote: > Hi all, > > We were trying to create programmatic parallel access to our appengine > application. > > From EC2, we were attempting (with threads) to run parallel access > (url gets/posts) to > our appid. There are some long running processes that we need to run > on EC2, for which > we would like to get a bunch of information (entities + processing on > appspot) quickly. > > We seem to be running into a limit on the number of accesses that are > allowed. > (4 threads seems to be the effective limit) > > Is there some sort of denial of service limit imposed on multiple > accesses from a single IP? > > Cheers, Gary > > -- > 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. > > > > > -- > Nick Johnson, Developer Programs Engineer, App Engine > Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: > 368047 > > -- > 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.
