I doubt gae scheduler counts the warmup time as billing front computing time now. I remember a googler ever said the warmup time is not counted as billing computing time.
Before migrating my app to modules style, gae scheduler counts my app's front end hours as 26.x hours. After the migration, gae scheduler counts my app's front end hours as 29.x hours. In the dashboard log, there are 340 /_ah/warmup requests in the last 24 hours. Each warmup request will spend 30 seconds. So it is about 170 minutes computing time or 3 hours. And 29.x - 26.x = 3. So I doubt gae scheduler counts the warmup time as billing front computing time now. On Saturday, January 25, 2014 3:23:40 PM UTC+8, Tapir wrote: > > My app doesn't encounter slowdown problem. > The problem is my app is over charged. > > On Saturday, January 25, 2014 1:45:47 PM UTC+8, Vinny P wrote: >> >> On Fri, Jan 24, 2014 at 8:43 PM, Tapir <[email protected]> wrote: >> >>> Before converting my app to modules style, the total front instance >>> hours were always less than 28 hours. >>> >> >> >> >> If you still have a copy of your app before you converted to modules, try >> uploading it and checking the performance. But this is most likely not the >> fault of the modules service: App Engine seems to be encountering a lot of >> "slowtime" this week, and you'll probably find that the errors smooth >> themselves out sooner or later. >> >> >> ----------------- >> -Vinny P >> Technology & Media Advisor >> Chicago, IL >> >> App Engine Code Samples: http://www.learntogoogleit.com >> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
