We are Python 2.5 (no concurrent). Yes, it seems the start-up time is just crazy high for at least some or all instances.
I also noticed that there are lot's of instances that served just 1 request and have average latency 0ms and have QPS=0 average instance age about 8-9 minutes (up to 11 minutes). For me it seems like an instance is created to serve static content and not used anymore and stays here until it die in a while. At the moment we have 264 active instances and it's killing our budget :( - see the screenshot attached. We had 2 hours downtime due to exceeded budget. Alex On Friday, 9 March 2012 15:57:27 UTC-4, Ikai Lan wrote: > > Alex, to answer that question: yes. We are looking to revamp the > production issues tracker which is far from optimal. When users can join or > aggregate issues, it allows us to quickly separate actual infrastructure > hiccups from user code issues. > > Thanks for the info! Is there any other behavior you can report? Does it > sound reasonable that you have 110-160 instances because of long startup > teams leading to more instances required to serve the same load? Are you > Python, Java or Go, and do you have concurrent requests enabled? > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > plus.ikailan.com > > > > On Fri, Mar 9, 2012 at 11:48 AM, Alexander Trakhimenok < > alexander.trakhime...@gmail.com> wrote: > >> Hey Ikai, >> >> Our app id: petaclasses >> >> QPS: 5-20 requests per second >> >> Current instances in dashboard: 110 - 160 >> Usual instances: 8-15 >> >> It's hard to say % of failed requests as we have also request that fail >> for other reasons (e.g. non existing pages, etc) and not sure how easily >> separate them. >> >> By the way, are you guys considering to create a page where we can >> post/report this data in some structured way and "join" an issue so you can >> accumulate and understand the scale of an issue easily. >> >> Alex >> >> >> On Friday, 9 March 2012 15:15:35 UTC-4, Ikai Lan wrote: >>> >>> Hey everyone, >>> >>> Here are a few things that will help: >>> >>> 1. Application IDs (<--- if you have nothing else, at least provide this) >>> 2. What is your QPS? >>> 3. What % of your requests are errors? >>> >>> -- >>> Ikai Lan >>> Developer Programs Engineer, Google App Engine >>> plus.ikailan.com >>> >>> >>> >>> On Fri, Mar 9, 2012 at 7:24 AM, Ronoaldo José de Lana Pereira < >>> rpere...@beneficiofacil.com.**br <rpere...@beneficiofacil.com.br>>wrote: >>> >>>> +1 for seeing the same problems on my app. >>>> >>>> It started to be worse after maintenance on March 7. >>>> >>>> Em sexta-feira, 9 de março de 2012 08h33min36s UTC-3, Nikolai escreveu: >>>> >>>>> +1 >>>>> we had to move to our backup systems. Everything is full of 500 errors >>>>> or hardcore latency. >>>>> Most of the 500 errors we see aren't even logged so this seems to be a >>>>> goole problem one abstraction layer above the app. >>>>> >>>>> And yes - sometimes we have got the same feeling, that we are the only >>>>> ones that use appengine in a production setting. You are not alone ;) >>>>> >>>>> regards, >>>>> nikolai >>>>> >>>>> Am Dienstag, 6. März 2012 22:17:37 UTC+1 schrieb Adam Sherman: >>>>>> >>>>>> Am I the only one seeing short duration outages? They are being >>>>>> reflected at: >>>>>> >>>>>> http://code.google.com/status/****appengine<http://code.google.com/status/appengine> >>>>>> >>>>>> But I don't see anyone else complaining anywhere, so it makes me >>>>>> worried. >>>>>> >>>>>> A. >>>>>> >>>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Google App Engine" group. >>>> To view this discussion on the web visit https://groups.google.com/d/** >>>> msg/google-appengine/-/**yixu1yAlMs4J<https://groups.google.com/d/msg/google-appengine/-/yixu1yAlMs4J> >>>> . >>>> >>>> To post to this group, send email to google-appengine@googlegroups.** >>>> com <google-appengine@googlegroups.com>. >>>> To unsubscribe from this group, send email to >>>> google-appengine+unsubscribe@**googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com> >>>> . >>>> For more options, visit this group at http://groups.google.com/** >>>> group/google-appengine?hl=en<http://groups.google.com/group/google-appengine?hl=en> >>>> . >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/google-appengine/-/ErrbHpuYmWgJ. >> >> 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. >> > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/DAWn9eldNmEJ. 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.
<<attachment: Screen Shot 2012-03-09 at 16.12.27.png>>
