Hello Andrew,
Here's a App Engine Groups discussion that is very similar to your question
(I posted a detailed and cited comment in the replies):
https://groups.google.com/forum/?fromgroups#!topic/google-appengine/5KRMpQ-9UQc
The short version is, what you're seeing is intended behavior. The idle
(also called resident) instance is there to buffer incoming requests; the
dynamic instance is launched and run to handle standard traffic.
-
-Vinny P
Technology Media Advisor
Chicago, IL
My Go side project: http://invalidmail.com/
On Thursday, June 6, 2013 2:39:21 PM UTC-5, Andrew Brogdon wrote:
I've got a small App Engine site built in Java, and I don't understand the
traffic splitting behavior that's going on. I have it set to maintain one
idle instance and spin up others as is sees fit. This, however, is what I
see in the Instances section of the dashboard:
*QPSLatency Requests Errors Age *
0.000 0.0 ms100 1 day, 1:56:27 (Idle)
0.083 162.0 ms 541 0 4:03:04 (Dynamic)
My idle instance is somehow dodging work, while the dynamic one is
handling almost all the requests. Why is this happening? If I'm only
going to be making use of one instance, I'd prefer to avoid having two, for
obvious reasons.
-Andrew
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
