Hi, To address some of the comments in this thread:
1 - Minor Versions - We did eliminate listing the minor version. This allows you to always access the latest changes for each version of your app at http://maj_ver.latest.app_id.appspot.com, instead of having to enter a new URL with each minor push. However, we understand that you would like some clarification as to what minor version is live in production, so we are planning on adding this number back to the 'Versions' column. 2. Concerning CPU accounting overall - The warning threshold for the logs and for the dashboard actually differ. In the logs, warnings will only occur for high runtime CPU. The warnings on the dashboard are triggered for high overall CPU, including CPU used in the runtime and per API, most notably being the datastore API. If you are curious to know where your resources are going for each request, we encourage you to use the Python Profiler: http://code.google.com/appengine/kb/commontasks.html#profiling This combined with the information in your dashboard and logs should allow you to pinpoint where any inefficiencies in your app may be. Also, please be aware as to how each column in the dashboard is calculated (details can be found on the FAQ: http://code.google.com/appengine/kb/general.html#currentload), but to reiterate some of the information: The number of requests for the handler is per day, calculated since Midnight PST. The %CPU is also calculated over the same time period. However, the Average CPU is only accounted for per hour. 3. High resource requests - We understand your application may have, on occasion, the need to consume more resources than normal - such as for parsing feeds or doing more complex calculations. As long as these calculations are relatively infrequent, this should not be a problem. Be sure to cache or store the results of the calculations for reuse to minimize the incidents of such requests. Quotas are not calculated on a per handler basis, but are per application. However, providing insight in to how specific requests consume resources allows you to optimize inefficient handlers. Hope this helps, Marzia On Thu, Sep 18, 2008 at 1:00 PM, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > I like the ease at which bottlenecks can be identified but what does > this mean: > > "This URI uses a high amount of CPU and may soon exceed its quota." > > Does each URI have its own quota now? Or are the quotas for the whole > application? Because I'm nowhere near using up my entire application > quota, but I get that warning for one of my URIs (which I knew was > inefficient). > > On Sep 18, 6:30 pm, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote: > > Hi, > > > > This morning we released a new Admin Console which includes a more > > descriptive accounting of your application's CPU stats. We now display > the > > amount of CPU consumed per request, as well as the avg amount of CPU used > > per handler. > > > > In addition to the CPU stats, you can see the short-term request rate per > > handler, as well as the total number of requests a day for each handler. > > > > Sign in to the admin console and check it out! > > > > -Marzia > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
