Hey, Here's a concrete example. One page load, 3 loading requests: one for the library page, another for a CSS file for that page, and a third for an image on that page. The end result, after a lot of optimization, is 24 seconds from initial page arrival to full display. And, it's likely that by the time the page has displayed, the JVM instance has shut down and the next user interaction will cause another loading request.
05-27 08:59AM 16.068 /resources/indira/img/buttons/share_o.png 200 4665ms 4160cpu_ms 1kb Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3,gzip(gfe) 05-27 08:59AM 20.707 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 request may thus take longer and use more CPU than a typical request for your application. 05-27 08:59AM 05.109 /resources/org.apache.wicket.Application/css/ tht.css 200 4014ms 3946cpu_ms 0kb Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3,gzip(gfe) 05-27 08:59AM 09.100 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 request may thus take longer and use more CPU than a typical request for your application. 05-27 08:58AM 56.380 /library;jsessionid=fU8dpFQMEe1Ec3BqNEY2vQ 200 8394ms 8142cpu_ms 170api_cpu_ms 3kb Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/ 3.6.3,gzip(gfe) 05-27 08:59AM 04.773 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 request may thus take longer and use more CPU than a typical request for your application. Thanks! Jake On Jun 7, 9:40 am, Jake <[email protected]> wrote: > Hey, > > The logs show what is being "GET" for any message. When loading some > pages, I noticed that, beyond the initial delay of the page, I saw an > 8s delay on one of the javascript files that was referenced in the > code. When I checked the GAE logs, I saw a startup request for the > initial GET for the HTML and then one immediately following GET for > the javascript file. I suppose it is possible that this was a new > instance spawning (instead of a restart), but I find that unlikely > since I was the only user of my application. Or, if it is the case > that GAE needs to spawn multiple JVMs to support one full page > request, I think that is a problem :) > > Anyways, end result is that from a period of inactivity with no > instances running, I went to my homepage once and saw two loading > requests in the logs right after one another for that single page > load. This has happened more than once. Granted, it's now been a > couple of weeks since I last tested this behavior, but I haven't heard > any feedback on my issue to suggest that it has changed. > > Jake > > On Jun 5, 8:45 pm, Thomas <[email protected]> wrote: > > > Hi Jake: > > > I am curious about how do you know there were 2 startup during one > > request? Did you submit an issue about the phenomenon? > > > On 6月6日, 上午2時34分, Jake <[email protected]> wrote: > > > > Hey Thomas, > > > > I get it all the time - to the point where all of my demonstration > > > applications are using the development server hosted on a non-GAE > > > machine :) Anyways, Ikai is (was) aware of the issue from awhile > > > back, but I'm not sure it's taking priority. > > > > Jake -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
