Sarang, are you doing any URL fetches, or some other API call that could be taking a long time (but not necessarily consuming CPU)?
If not, then given the numbers you've posted (ie. 100's of seconds latency with < 1 CPU second consumed), it does look like there could be something wrong with the GAE production servers. Nick On 24 May 2011 06:29, Brandon Wirtz <[email protected]> wrote: > No. It’s the You aren’t getting any traffic so we aren’t sitting around > with empty services to wait for you, feature. > > > > And the variation of that feature is, the Pay for us to sit around and wait > for you and we will always have an instance waiting for you. > > > > Also remember that an instance in the cloud is 1.2 ghz single “Core” if > you are running a process on your local machine you could be 10x that speed. > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Sarang Lakare > *Sent:* Monday, May 23, 2011 1:18 PM > > *To:* [email protected] > *Subject:* Re: [google-appengine] Poor performance since the past 2-3 days > > > > Ok, but I still don't understand why it should take 100 - 500 seconds for > the load request to complete! Isn't that a bug? > > > > Sarang > > On Tue, May 24, 2011 at 1:33 AM, Brandon Wirtz <[email protected]> > wrote: > > Pay for always on, it will go away. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Sarang > *Sent:* Monday, May 23, 2011 12:52 PM > *To:* [email protected] > *Subject:* [google-appengine] Poor performance since the past 2-3 days > > > > I have a python/django app that works blazing fast on the dev_appserver > locally, but is taking painfully long to load on GAE since the last 2-3 > days. Can anyone please let me know how to resolve it? > > > > Here are the issues: > > > > 1. I routinely get > > > 1. 2011-05-23 12:17:06.505 / 200 373876ms 793cpu_ms 15kb AppEngine-Google; > (+http://code.google.com/appengine) > > 0.1.0.1 - - [23/May/2011:12:17:06 -0700] "GET / HTTP/1.1" 200 15939 - > "AppEngine-Google; > > ... > > 2. I2011-05-23 12:17:06.505 > > 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. > > > > See more within the half hour: > > > 2011-05-23 12:18:09.581 / 200 3062ms 653cpu_ms 15kb AppEngine-Google; (+ > http://code.google.com/appengine) > 2011-05-23 12:17:06.505 / 200 373876ms 793cpu_ms 15kb AppEngine-Google; (+ > http://code.google.com/appengine) > 2011-05-23 12:12:43.657 / 500 167275ms 70cpu_ms 1kb Mozilla/5.0 (Windows > NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 > Safari/534.24,gzip(gfe),gzip(gfe),gzip(gfe) > 2011-05-23 11:43:12.087 / 200 503348ms 746cpu_ms 15kb AppEngine-Google; (+ > http://code.google.com/appengine) > > all these for my landing page which loads in a few milliseconds on the > local server. > > I have taken all the precautions documented: cron job, main() in python > code, etc. I have the keep_alive cron job running every 1 minute. However, I > have observed that many times it does not start every minute and that leads > to high load times. Example: > > > > > 2011-05-23 12:07:49.777 / 200 2999ms 23cpu_ms 15kb AppEngine-Google; (+ > http://code.google.com/appengine) > > > 2011-05-23 12:06:46.769 / 200 13ms 0cpu_ms 15kb AppEngine-Google; (+ > http://code.google.com/appengine) > 2011-05-23 12:05:46.749 / 200 11ms 23cpu_ms 15kb AppEngine-Google; (+ > http://code.google.com/appengine) > > You can observe that the when the spacing between cron jobs is > 1minute, > the load times suddenly increase. > > > > My 2 key questions: > > > > 1. Any way for me to profile and find out where the app engine gets stuck > when I get those enormously large load times? > > 2. Any way to ensure cron is fired within a minute? > > Appreciate any help. > > > > Regards, > > Sarang > > -- > 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. > > -- > 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. > > > > > -- > --------------------------------------------------- > Sarang Lakare, Ph.D. > > myContactID: **2010-1399-1401* <http://mycid.in/add/201013991401> > > > > -- > 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. > > -- > 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. > -- 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.
