I have a multithreaded java app on gae. I find that with only a relatively 
small concurrency gae will start a new instance. This occurs even if I wind the 
latency up to 15s in 
the console.

Can some one describe how gae decides whether to dispatch a request to a new 
thread vs new to start a new instance. In particular how is a multithreaded app 
instance determined to be busy?

thx.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine-java/-/N5lPx6d-tSAJ.
To post to this group, send email to google-appengine-java@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.

Reply via email to