Jeff, I see very similar behaviour in pythonland - i.e., the resident instance gets almost no traffic. I opened an Enterprise support ticket on the topic, and I got the following response:
"the Resident instances are kept alive by the GAE scheduler for long periods in order to attend to new requests whenever there are no Dynamic instances to serve them. In this way, the request does not have to wait for the instance creation, thus, the latency of creating the instance is avoided. However, as soon as the new Dynamic instance is up and running, it starts getting requests and the Resident instance turns idle again, until the app sees more traffic than its available Dynamic instances are able to serve." Frankly, I'm not totally sure when the resident instances actually get traffic. I flipped on a resident instance just so that I could get warmup requests back (they are only issued if you have resident instances now), but now I have an instance floating around doing very, very little work. It just seems wrong to me. j -- 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.
