tag:blogger.com,1999:blog-4311234419396881619.post5945373874696965240..comments2009-05-04T16:32:47.655+02:00Stringbuffer.comhttp://www.blogger.com/profile/13625967709587703071noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4311234419396881619.post-11435772386926751142009-05-04T16:32:00.000+02:002009-05-04T16:32:00.000+02:00140ms (1.2GHZ CPU) per request.<br /><br />But what can you do with 140cpums? How many cpums for a simple servlet which returns 6,400 bytes. How many cpums for a single datastore call which finds a single entity?<br /><br />If the datastore is busy then your process spin/waits and you are charged for the cpu time.<br /><br />What I am wondering is, what can a 'reasonably efficient' web app achieve in 140cpu-ms, and is that reasonable?yohttp://www.blogger.com/profile/03076771604056633441noreply@blogger.comtag:blogger.com,1999:blog-4311234419396881619.post-88967004003270343252009-05-04T15:54:00.000+02:002009-05-04T15:54:00.000+02:00Great series of posts, really enjoying this blog.<br /><br />Could you investigate gzip compression? There is a trade-off between bandwidth and cpu usage when gzip compression is used for dynamic pages.<br /><br />Paul Buchheit (GMail creator) says that this trade-off favours using cpu for gzip over bandwidth:<br /><br />http://paulbuchheit.blogspot.com/2009/04/make-your-site-faster-and-cheaper-to.html<br /><br />However, for Appengine/Python, although static resources like css and javascript are automatically served compressed, dynamic pages aren't, and you cannot do it manually as Content-Encoding response headers are stripped by the server.<br /><br />The Appengine/J docs don't make the distinction between compressing dynamic/static content, but they imply that dynamic content is compressed.<br /><br />Is this the case? Does Appengine/J compress dynamic content and how does that change the budget for cpu/bandwidth allowance and price per request?yohttp://www.blogger.com/profile/03076771604056633441noreply@blogger.com