On Saturday, January 25, 2014 9:09:02 AM UTC+8, timh wrote: > > Irrespective of what your view of the definition of an idle instance and a > resident instance is, thats not how google see's it. > Resident and Dynamic instances are different. > > In addition > > A resident instance may or may not service a request. > An idle (dynamic) instance (not resident) is most likely to service a new > request. > You may have extra idle (dynamic) instances that are created (due to a > perceived demand) and never service a request. > You are not charged for idle (dynamic) instances above max idle. > > Idle (dynamic) instances are in addition to any resident instance. >
In this docs: https://developers.google.com/appengine/docs/adminconsole/instances it clearly shows *minimum idle instances* is for control the number of *resident instances*: App Engine also offers *resident* instances, which remain running all the time. Resident instances allow you to improve application performance, and, if your application uses backends, allow you to perform longer-running, larger tasks. You can enable resident instances on a backend<https://developers.google.com/appengine/docs/python/backends>, or by setting minimum idle instances<https://developers.google.com/appengine/docs/adminconsole/performancesettings> . So I think idle instance == resident instance. > > Here is a list of instances from a low traffic site > > *Instances *[image: > help]<https://developers.google.com/appengine/docs/adminconsole/instances> > QPS*Latency*RequestsErrorsAgeMemoryApp Engine ReleaseLogsAvailability > Shutdown0.0000.0 ms29502 days, 5:44:0869.8 MBytes1.8.9 > [image: Resident Icon]Resident > 0.050350.7 ms1546016:34:2155.3 MBytes1.8.9 > [image: Dynamic Icon]Dynamic > 0.0000.0 ms5302:37:2470.6 MBytes1.8.9 > [image: Dynamic Icon]Dynamic > > Look at your instances chart to see what you aggregate instance time you > are being billed for. > > If you really want to keep under the 28 hours (I have done it in the past) > (you probably shouldn't use java ;-). > > > - Don't have a reserved instance, set idle instances to one, and run a > external wget every minute or so to keep a single instance alive. > - If new instances take too long to start and another request comes in > during startup, then you will probably find you get another dynamic > instance started. > > T > > T > > On Saturday, January 25, 2014 8:54:52 AM UTC+8, Tapir wrote: >> >> >> >> On Saturday, January 25, 2014 2:06:31 AM UTC+8, Rafael Sanches wrote: >>> >>> that seems correct, >>> >>> You have one idle instance because of this: <max-idle-instances>1</max- >>> idle-instances> >>> >>> You have one resident instance because of this: >>> <min-idle-instances>1</min-idle-instances> >>> >> >>> You have one other instance because that's the one that is actually >>> serving. >>> >>> >>> >> What is the difference between idle instance and resident instance in >> your view? They are different concepts? or the same? >> You think there are only one dynamic instance running? >> (In my view, idle instance and resident instance are the same concept. >> There is only one resident/idle instance there. And there are 2 dynamic >> instances running) >> >> Do you think a dynamic instances opened for hours to handler just 2 >> requests (one is /_ah/warnup) is normal? >> >> >> >> >>> >>> >>> On Fri, Jan 24, 2014 at 8:20 AM, Tapir <[email protected]> wrote: >>> >>>> Evidence: http://imgur.com/VNHdkpU >>>> >>>> Following is the config. >>>> >>>> <?xml version="1.0" encoding="utf-8"?> >>>> <appengine-web-app xmlns="http://appengine.google.com/ns/1.0"> >>>> <application>{{app_id}}</application> >>>> <module>default</module> >>>> <version>{{app_version}}</version> >>>> >>>> <!-- loading faster --> >>>> <precompilation-enabled>true</precompilation-enabled> >>>> >>>> <!-- warmup --> >>>> <warmup-requests-enabled>true</warmup-requests-enabled> >>>> >>>> <!-- concurrentcy --> >>>> <threadsafe>true</threadsafe> >>>> >>>> <!-- concurrentcy --> >>>> <sessions-enabled>true</sessions-enabled> >>>> >>>> <inbound-services> >>>> <service>channel_presence</service> >>>> </inbound-services> >>>> >>>> <!-- scale settings --> >>>> >>>> <instance-class>F1</instance-class> >>>> >>>> <automatic-scaling> >>>> <min-idle-instances>1</min-idle-instances> >>>> <max-idle-instances>1</max-idle-instances> >>>> <min-pending-latency>2730ms</min-pending-latency> >>>> <max-pending-latency>automatic</max-pending-latency> >>>> <max-concurrent-requests>50</max-concurrent-requests> >>>> </automatic-scaling> >>>> >>>> <!-- Configure java.util.logging --> >>>> <system-properties> >>>> <property name="java.util.logging.config.file" >>>> value="WEB-INF/logging.properties"/> >>>> </system-properties> >>>> >>>> <static-files> >>>> <include path="/favicon.ico" /> >>>> <include path="/crossdomain.xml" /> >>>> <include path="/css/**.*" expiration="1d"/> >>>> <include path="/swfs/**.swf" expiration="365d" /> >>>> <include path="/js/**.js" expiration="1d" /> >>>> <include path="/images/**.ico" expiration="1d" /> >>>> <include path="/images/**.png" expiration="1d" /> >>>> <include path="/images/**.gif" expiration="1d" /> >>>> <include path="/images/**.jpg" expiration="1d" /> >>>> <include path="/htmls/**.i*" expiration="1d" /> >>>> </static-files> >>>> >>>> </appengine-web-app> >>>> >>>> >>>> -- >>>> 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 [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at http://groups.google.com/group/google-appengine. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
