I don't believe your use case should be a load problem. My users ( www.ninuku.com) are querying collections containing hundreds of instances and extents that contain tens of thousands of instances usually within the 1000 msec threshold I've been tuning to. I'm getting between 1% and 2% "waiting too long" responses on a normal day both on the external hits and internal task queue hits.
Your second error (203) is usually the case when your app leaks a serious runtime exception or error and app engine decides to restart that instance. I've noticed that app engine sometimes has a hard time starting up new app instances from none and the 500 errors will stack up until one comes fully online. I've had to bullet proof my UI requests with retry loops since my customers get a bad taste from 500 responses. The only naked requests the browser makes are to static files since they always serve up fast and reliably. My suggestion to you is the load up appstats and tune the external request durations to a max 1000ms in order to not get throttled. http://googleappengine.blogspot.com/2010/03/easy-performance-profiling-with.html Also if you are using task queues, try to keep task hit durations under 10 seconds for the same reason. App engine likes things to be quick. Good luck, --Stevko On Tue, Nov 30, 2010 at 3:19 PM, MdeA <[email protected]> wrote: > Thanks Stevko. I took a look at that Issue and now I think something > is definitely wrong with the availability of the system. > I don't know the rest of the people having this problem, but I'm not > using anything sophisticated on those pages. > The only I can think of is the queries against the Datastore, but if > running a query against a "table" with around 100 "records" and 40 > "columns" to return 2 or 3 (max 12) records causes problems like this; > then, we have a problem. > The most basic relational DB would handle that in a breeze. > You shouldn't have to go through the pain of implementing > "caching" (what I've been told) for something as simple as that. > > On Nov 30, 1:17 pm, "A. Stevko" <[email protected]> wrote: > > @micdearmas, > > These are pretty much a fact of life these days. > > I suggest star'ing this issuehttp:// > code.google.com/p/googleappengine/issues/detail?id=2396#c34 > > <http://code.google.com/p/googleappengine/issues/detail?id=2396#c34> > > > > <http://code.google.com/p/googleappengine/issues/detail?id=2396> > > > > > > > > > > > > > > > > On Tue, Nov 30, 2010 at 9:11 AM, MdeA <[email protected]> wrote: > > > I know this is the million dollars question , but does anybody know > > > what's the best way to contact the App Engine team. I'm getting some > > > error msgs(below) that suggest you do that. > > > I'm getting these messages and they seem to happen when no request has > > > been received for some time. > > > Also, my use of the free quotas don't surpass the 2%. However, I'm > > > investing (with AdWords) to get my site promoted and I need to make > > > sure that I have a responsive Engine running my application. > > > Thanks in advance for your time and consideration. > > > Michael > > > > > airport-parking-cheap.appspot.com > > > ... > > > - Request was aborted after waiting too long to attempt to service > > > your request. This may happen sporadically when the App Engine serving > > > cluster is under unexpectedly high or uneven load. If you see this > > > message frequently, please contact the App Engine team. > > > ... > > > - A serious problem was encountered with the process that handled this > > > request, causing it to exit. This is likely to cause a new process to > > > be used for the next request to your application. If you see this > > > message frequently, you should contact the App Engine team. (Error > > > code 203) > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Google App Engine" group. > > > To post to this group, send email to [email protected] > . > > > To unsubscribe from this group, send email to > > > [email protected]<google-appengine%[email protected]><google-appengine%2Bunsubscrib > [email protected]> > > > . > > > 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > 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 [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?hl=en.
