About 30% visits will encounter cold startup. Why AppEngine doesn't triy to use the resident instance but often try to create a new instance to handle new visits?
This problem doesn't happen before, but it is serious today. On Feb 27, 2:31 pm, Tapir <[email protected]> wrote: > Many such logs: > > A serious problem was encountered with the process that handled this > request, causing it to exit. This is likely to cause a new process to > be used for the next request to your application. If you see this > message frequently, you may be throwing exceptions during the > initialization of your application. (Error code 104) > > There are 2 instances running for about one hour: > 0.000 0.0 ms 30 1 0:43:54 98.5 MBytes Resident Icon > Resident > 0.000 0.0 ms 10 0 1:25:04 95.1 MBytes Dynamic Icon > Dynamic > > The visits of my app is very small, about one pageview/minute. > The 2 running instances are idle at most time. > But AppEngine still often tries to create a third one even if the 2 > running ones are idle so that there are many long-time instance > startups. -- 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.
