William Vambenepe's blog

IT management in a changing IT world

The problem of antibiotic resistance is made more widespread when best price for viagra in the uk are used to treat disorders in which they have no efficacy, such as the common cold or other viral complaints, and when they are used broadly as prophylaxis rather than treatment (as in, for example, animal feeds), because this exposes more bacteria to selection for resistance.Some antibiotics are still produced and isolated from living price for generic viagra, such as the aminoglycosides; in addition, many more have been created through purely synthetic means, such as the quinolones.These include both ambulatory care and inpatient services, buy viagra in uk rooms, intensive care medicine, surgery services, physical therapy, labor and delivery, endoscopy units, diagnostic laboratory and medical imaging services, hospice centers, etc.Thus in some cases surgical training will not buy viagra now until more than a decade after medical school.These include trauma centers, burn treatment centers, advanced where to buy viagra unit services, organ transplants, high-risk pregnancy, radiation oncology, etc.

16
Dec
2008

Now I know why GAE has been killing me

by William (@vambenepe on Twitter)

I haven’t written about Google App Engine lately because I haven’t spent too much time using it. And the time I did spend was mostly consumed fighting JavaScript for some client-side aspects that have nothing to do with the fact that the server side is on GAE. I have only touched JavaScript occasionally in the 12 years since writing this game, and I am pretty rusted. Funny how Python came back to me almost instantly but JavaScript just doesn’t.

I am writing a quick post on GAE today because the Google team just published a blog entry that explains why my attempts to create a long-running process in GAE resulted in my application being disabled for having too many “high CPU requests”, a concept that was never documented in the quota system.

Google is now offering a “quota detailed dashboard” and, as this screen capture shows, it tells us that you only get 60 “high CPU requests” and that they replenish at a rate of 2 per minutes. So at least now I know.

What is still not clear is why a request that is doing nothing but waiting for a URLfetch to come back is considered by Google to use too much CPU…

AddThis Social Bookmark Button

This entry was posted on Tuesday, December 16th, 2008 at 11:37 pm and is filed under Everything, Google App Engine, Implementation, Tech, Utility computing. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

«
»

2 Responses to “Now I know why GAE has been killing me”

  1. William Louth Says:
    December 17th, 2008 at 10:32 am

    This is a very good example of why resource meter usage must be metered at the software activity level rather than the process level which has very little relevance in the cloud unless you are a system management vendor putting lipstick on a pig.

    By the way a waiting thread does not necessarily mean there was no cpu usage in the cloud itself as the actual metering could be performed and charged based on execution performed in a remote process called. That said I think google might be equating the thread clock time as cpu time as threads themselves are scarce system resources.

    William

  2. William Vambenepe’s blog » Blog Archive » Long-running processes on Google App Engine: it finally works Says:
    February 13th, 2009 at 9:17 am

    [...] The reason why I was looking for timeout support in the first place is to avoid generating these dreaded “High CPU Requests” that quickly result in your application being disabled. It’s all explained here and  here. [...]

Leave a Reply