In addition here the failed-request report from Pingdom the last day (that's not acceptable!):
al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 3:16 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 3:16 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 3:34 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 3:35 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 17:44 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 17:45 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 17:57 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 17:58 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 18:17 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 18:18 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 18:34 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 18:35 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 18:43 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 18:44 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 19:02 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 19:03 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 19:05 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 19:05 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 19:41 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 19:42 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 19:51 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 19:52 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 20:02 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 20:05 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 20:10 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 20:12 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 23:03 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 23:04 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 23:10 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 23:10 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN Mi 23:15 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP Mi 23:16 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN 02:48 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP 02:49 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN 03:04 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP 03:06 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN 03:12 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP 03:13 6 KB krisentalk al...@pingdom.com DOWN alert: krisentalk (www.krisentalk.de) is DOWN 06:25 6 KB krisentalk al...@pingdom.com UP alert: krisentalk (www.krisentalk.de) is UP 06:26 6 KB krisentalk On Wed, Aug 22, 2012 at 9:58 PM, Mos <mosa...@googlemail.com> 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. > > It's very obvious that one instance should be enough for my application. > And that was almost the case the last months! > > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
