Hi Mos, On Thu, Aug 23, 2012 at 4:58 AM, Mos <[email protected]> wrote:
> Does anybody else experience abnormal behavior of the instance-scheduler > the last three weeks (the last 7 days it got even worse)? (Java / HRD) > Or does anybody has profound knowledge about it? > > Background: My application is unchanged for weeks, configuration not > changed and application's traffic is constant. > Traffic: One request per minute from Pingdom and around 200 additional > pageviews the day (== around 1500 pageviews the day). The peek is not more > then 3-4 request per minute. > A possible explanation could be that the traffic pattern had changed. > > It's very obvious that one instance should be enough for my application. > And that was almost the case the last months! > Actually it's not true. In particular, check this log: https://appengine.google.com/logs?app_id=s~krisen-talk&version_id=1-0.360912144269287698&severity_level_override=1&severity_level=3&tz=Europe%2FBerlin&filter=&filter_type=regex&date_type=datetime&date=2012-08-23&time=23%3A57%3A00&limit=20&view=Search You can see the iPhone client repeatedly requests your dynamic resources in a very short amount of time. Presumably it's due to some kind of 'prefetch' feature of that device. Are you aware of those accesses, and that this access pattern can cause a new instance starting? I don't think this is the only reason, but this can explain that some portion of your loading requests are expected behavior. Now I'd like to ask you some questions. * What is the purpose of max-pending-latency = 14.9 setting? * Can you try automatic-automatic for idle instances setting? * What is the purpose of those pingdom check? What happens if you stop that? > > But now GAE creates most of the time 3 instances, whereby on has a long > life-time for days and the other ones are restarted around > 10 to 30 times the day. > Because load request takes between 30s to 40s and requests are waiting > for loading instances, there are many request that > fail (Users and Pingdom agree: *A request that takes more then a couple > of seconds is a failed request!*) > > Please check the attached screenshots that show the behavior! > > Note: > - Killing instances manually did not help > - Idle Instances were ( Automatic – 2 ) . Changing it to whatever didn't > not change anything; e.g. like ( Automatic – 4 ) > > Thanks and Cheers > Mos > > > > > > > -- > 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. > -- Takashi Matsuo | Developers Advocate | [email protected] -- 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.
