And there is a form you can fill out to have your request per second limit increased if that is a need.
http://code.google.com/support/bin/request.py?contact_type=AppEngineCPUReque st Just explain why you need more resources and they will be granted. Even 100k people showing up with in a 5 minute time frame is only 333 requests a second. You should have a hard time hitting the 500 QPQ limit. Also you can round robin portions of your cycles by putting a request proxy ahead of your large app so that you are less restricted by these already generous limits. Is anyone actually hitting Thread limit errors? Or is this just a typical I'm going to be the next Facebook OMG Google won't work for this when I get to 1.2m active users guess I should build my own server in my basement because it will be better, sort of naval gazing that I face with PMs and SysArc's on a regular basis? You can't break the speed of light with a Jet Engine either, but its still over kill for my soapbox derby car. -Brandon Wirtz -----Original Message----- From: google-appengine@googlegroups.com [mailto:google-appeng...@googlegroups.com] On Behalf Of Jeff Enderwick Sent: Wednesday, September 02, 2009 12:40 PM To: google-appengine@googlegroups.com Subject: [google-appengine] Re: 30 Max simultaneous requests (maxThreads)? There are application domains that spike severely. One example is AAA for corporate environments. There are large companies on the planet where *everyone* comes to work @ 8am +/-10min and logs in. Just one example from a prior life... --~--~---------~--~----~------------~-------~--~----~ 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-appengine@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 -~----------~----~----~----~------~----~------~--~---
