FWIW, warmup requests and instance startup has been very very inconsistent 
the past couple of weeks. I've had an app that usually took 2-3S show up in 
the logs as DeadLineExceeded and causing our integration tests to fail when 
originating from the continuous integration server and it's very sporadic. 
So I think AE has been more than marginally slower as of late.

I think the lesson learned is to avoid starting up new instances, and put 
your whole app in one small file. :)


On Friday, April 13, 2012 10:51:15 AM UTC-4, Jeff Schnitzer wrote:
>
> Right.  The problem is the 61244ms that it takes to start your app.  How 
> long does it normally take?
> Look at past warmup requests (the ones that work) and see how long they 
> take.  My guess is that
> the number is close to 60s.  If GAE gets marginally slower, it pushes you 
> over the edge.
>
> As for why your app takes so long to startup, I can't begin to speculate. 
>  What does it do at startup?
> Do any of your frameworks do classpath scanning?  Do you have a lot of big 
> jars?  Zillions of
> class files?  Do you load data from the datastore or blobstore?
>
> You need to diagnose the warmup requests that *do* work.  Sure, look at 
> appstats - although
> that will only show issues if your warmup fetches data from services (ie, 
> not the filesystem).
> However, you really should be able to think about it a few minutes and 
> figure out the problem.
> App startup is almost 100% deterministic.  There are no parameters.  You 
> know what it does.
>
> Jeff
>
> On Fri, Apr 13, 2012 at 9:55 AM, Rui Oliveira <[email protected]>wrote:
>
>>  Hi Jeff
>>>
>>> Thanks for your replay. Your answer was very important for me to start 
>>> looking to the right part of the problem. 
>>>
>>>  Just to clarify :"startup time" is the time to start a new instance 
>>> right?
>>>
>>> How can I analyze the startup time inside the server? I'm looking to the 
>>> appengine logs, appstats, and speedtracer, but in none of them I can find 
>>> whats happening during the startup.
>>>
>>>  If I deploy the program I'm getting this kind of logs:
>>>
>>>
>>    1. 012-04-13 11:33:35.889 /_ah/warmup 500 6**1244ms 0kb 
>>    2. W2012-04-13 11:33:35.787 EXCEPTION 
>> com.google.apphosting.api.**DeadlineExceededException: 
>>    This request (08f66682e6ba5919) started at 2012/04/13 11:32:35.741 UTC 
>> and 
>>    was still e 
>>    3. E2012-04-13 11:33:35.790 javax.servlet.**ServletContext log: 
>>    unavailable javax.servlet.**UnavailableException: This request 
>>    (08f66682e6ba5919) started at 2012/04/13 11:32:35.741 U 
>>    4. W2012-04-13 11:33:35.810 Failed startup of context 
>>    com.google.apphosting.utils.**jetty.**RuntimeAppEngineWebAppContext@**
>>    1811e2c{/,/base/data/home/**apps/s~airmenudemo/29.**358177921953 
>>    5. C2012-04-13 11:33:35.816 Uncaught exception from servlet 
>>    javax.servlet.**UnavailableException: Initialization failed. at 
>>    com.google.apphosting.runtime.**jetty.AppVersionHandlerMa 
>>    6. I2012-04-13 11:33:35.819 This request caused a new process to be 
>>    started for your application, and thus caused your application code to be 
>>    loaded for the first time. This requ 
>>    7. W2012-04-13 11:33:35.819 A 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 nex 
>>
>>  
>>
>>> On appstats: ( 
>>> http://www.airmenudemo.**appspot.com/appstats/stats<http://www.airmenudemo.appspot.com/appstats/stats>
>>>  )
>>>
>>>  (16) 2012-04-13 11:36:31.587 "GET /appstats/" 307 
>>> <http://www.airmenudemo.appspot.com/appstats/details?time=1334316991587>real=215ms
>>>  
>>> api=0ms overhead=0ms (0 RPCs)
>>>
>>>  (17) 2012-04-13 11:35:49.207 "GET /symbolmanifest.json" 404 
>>> <http://www.airmenudemo.appspot.com/appstats/details?time=1334316949207>real=609ms
>>>  
>>> api=0ms overhead=0ms (0 RPCs)
>>>
>>>  (18) 2012-04-13 11:27:25.255 "GET /_ah/warmup" 200 
>>> <http://www.airmenudemo.appspot.com/appstats/details?time=1334316445255>real=441ms
>>>  
>>> api=0ms overhead=0ms (0 RPCs)
>>>
>>> As you can see after deploy the appstats don't log nothing.
>>
>> After deploy I can't even open appstats.
>>
>> After some minutes / hours everything starts ok.
>>
>> Thanks
>>
>> Rui
>>
>>>  -- 
>> 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/-/frES_he8DHYJ.
>>
>> 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.
>>
>
>

-- 
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/-/nVN_RoUpA7sJ.
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.

Reply via email to