Can that be clarified a bit? GAE concurrent requests are capped below 10 and 1/3 sec response time is considered a long request? This doesn't seem realistic compared to non-trivial 3-tier JEE clusters where an installation might support upwards of 100+ open sockets and a looong transaction might run 800+ ms (4 secs client wait time being an accepted max before resorting to async mechanisms). That's in the context of modern processors, which seem faster than the GAE CPU algorithms. Is there a roadmap to support such requirements or is that being relegated to the hosted image model of cloud computing?
On Dec 10, 2009 7:48 PM, "Ikai L (Google)" <ika...@google.com> wrote: 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 <adma...@gmail.com> wrote: > > I have a simple application tha... -- Ikai Lan Developer Programs Engineer, Google App Engine -- You received this message because you are subscribed to the Google Groups "Google App Engine f... -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
