There is a limit on the number of open connections you can have, and it could be that you are hitting this limit. App Engine favors a model where you use many small, cheap requests in lieu of single, long requests.
On Tue, Dec 8, 2009 at 2:50 PM, R D <[email protected]> wrote: > I have a simple application that I use for our load testing. The > servlet simply sleeps for 300ms and returns a small HTML response back > to the calling program. There is nothing else involved here. No DB > calls as well. > > Response time under extremely moderate load - 10 simultaneous requests > is in 2-3 second range (this is from the logs on app engine > dashboard). > > I have enabled billing for this app so that I can get more requests/ > secs. > > What am I missing here? > > RD > > -- > > 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 > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > > -- Ikai Lan Developer Programs Engineer, Google App Engine -- 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 [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-java?hl=en.
