Comments on: Now I know why GAE has been killing me http://stage.vambenepe.com/archives/475 IT management in a changing IT world Mon, 26 Jul 2010 20:24:03 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: William Vambenepe’s blog » Blog Archive » Long-running processes on Google App Engine: it finally works http://stage.vambenepe.com/archives/475#comment-62104 William Vambenepe’s blog » Blog Archive » Long-running processes on Google App Engine: it finally works Fri, 13 Feb 2009 17:17:08 +0000 http://stage.vambenepe.com/?p=475#comment-62104 [...] 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. [...] [...] 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. [...]

]]> By: William Louth http://stage.vambenepe.com/archives/475#comment-56709 William Louth Wed, 17 Dec 2008 18:32:46 +0000 http://stage.vambenepe.com/?p=475#comment-56709 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 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

]]>