Hi Jeff You provided so little information I had no idea how experienced you are with the platform so provided you with some pointers of things to look at.
And Kenneth is pretty much spot on, re: instances spinning up. As he points out if you can get you avg request time down low you might find you don't need to spin up as many instances. And one of the best ways to do this is aggressive caching. T On Aug 30, 7:47 pm, Jeff Schwartz <[email protected]> wrote: > While what you say is true, Tim, memcache is not always the proper > persistence layer or solution for solving these problems. If the processing > that is exceeding quota is geared towards all users then yes, memcache can > be helpful but if the processing is user specific then session state is the > better solution. And of course, breaking up requests into smaller ones and > firing off multiple requests and or task to process them will be required > also. > > For instance, take displaying a page of status updates in a fanout type of > application. Instead of acquiring all the status update entities to render > the page it would be better to acquire all the keys to the entities, store > them in session state and send back 1 or 2 entities to the client where they > will render and where an ajax routine will then be kicked off to go out and > retrieve & render the remaining entities 1 at a time. Breaking things down > like this can reduce the need to use tasks as well. > > Jeff > > > > > > > > > > On Mon, Aug 30, 2010 at 7:33 AM, Tim Hoffman <[email protected]> wrote: > > Hi > > > You haven't provided any information to help use give you hints. > > > But basically whatever you are doing is taking too long. > > > You should look at the stack trace to see where in you code things are > > stopping. > > You should probably also look at appstats and profile what you > > application is doing and > > work at making things more efficient (including but not limited to > > caching with memcache) > > > T > > > On Aug 28, 4:20 am, rishi <[email protected]> wrote: > > > I keep getting the following error sometimes, but today its happening > > > too often which is causing lot of issues on my cloud. Please let me > > > know how this could be fixed. > > > > 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. > > > -- > > 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%2Bunsubscrib > > [email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. > > -- > -- > Jeff -- 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.
