I am little confused with how these instances work. How long does an instance stay alive? A site in Python 2.5 (M/S) fires up an instance when it is accessed and the instance stays alive for minutes after. With Python 2.7(HRD) the instance is killed off after a matter of seconds. So I either have to pay and keep the application alive but then it gets tricky. And to add insult to injury, if I access a python 2.7 application and get one page, the instance lasts for a few seconds but I am billed for 15 minutes. If I am billed for 15 minutes please would it be possible for the instance to stay alive for something close to 15 minutes?
Now if I enable billing (for the cost of $2.10 a week). I can adjust the sliders under application settings, I have two settings "Idle instances" and "Pending latency". Leaving "Idle instances" at Automatic results in instances only lasting a few seconds. Setting it to 1 results in having a "Resident" instance and this sort of works. I can use the application a little but then a second instance fires up and leaves one instance completely idle. All I want is one instance running. I put "Pending Latency" up to 500ms to try and stop other instances firing up. I use the application and so now I have two instances serving, The resident instance is sitting there doing nothing and I am using another instance but being billed for both. So I go an play with the sliders and set idle instances to automatic and it kills one off (the resident one that was doing nothing). But then the instances start with their stop start routine and the application is very unresponsive. Is there a bug with the instancing or is there something that I really don't understand here. -- 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.
