<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Google App Engine Announces Pricing</title>
	<atom:link href="http://gigaom.com/2009/02/24/google-app-engine-announces-pricing/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2009/02/24/google-app-engine-announces-pricing/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 13:40:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Google Aims to Woo the Enterprise With Its Cloud [GigaOM] &#124; BYOHosting.com Blogs</title>
		<link>http://gigaom.com/2009/02/24/google-app-engine-announces-pricing/#comment-161969</link>
		<dc:creator><![CDATA[Google Aims to Woo the Enterprise With Its Cloud [GigaOM] &#124; BYOHosting.com Blogs]]></dc:creator>
		<pubDate>Mon, 04 May 2009 14:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=40633#comment-161969</guid>
		<description><![CDATA[[...] and didn&#8217;t allow users to consume of a lot of resources without permission. Google started charging developers to use App Engine three months ago, and earlier this month added to it support for Java, a programming language [...]]]></description>
		<content:encoded><![CDATA[<p>[...] and didn&#8217;t allow users to consume of a lot of resources without permission. Google started charging developers to use App Engine three months ago, and earlier this month added to it support for Java, a programming language [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Aims to Woo the Enterprise With Its Cloud</title>
		<link>http://gigaom.com/2009/02/24/google-app-engine-announces-pricing/#comment-161968</link>
		<dc:creator><![CDATA[Google Aims to Woo the Enterprise With Its Cloud]]></dc:creator>
		<pubDate>Mon, 04 May 2009 04:01:10 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=40633#comment-161968</guid>
		<description><![CDATA[[...] and didn&#8217;t allow users to consume of a lot of resources without permission. Google started charging developers to use App Engine three months ago, and earlier this month added to it support for Java, a programming language [...]]]></description>
		<content:encoded><![CDATA[<p>[...] and didn&#8217;t allow users to consume of a lot of resources without permission. Google started charging developers to use App Engine three months ago, and earlier this month added to it support for Java, a programming language [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://gigaom.com/2009/02/24/google-app-engine-announces-pricing/#comment-161967</link>
		<dc:creator><![CDATA[Pete]]></dc:creator>
		<pubDate>Wed, 25 Feb 2009 02:55:37 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=40633#comment-161967</guid>
		<description><![CDATA[Great questions.  Our mechanism for metering CPU usage is outlined here:

http://code.google.com/appengine/docs/quotas.html#Requests

Essentially, we use a generic 1.2 GHz Intel x86 processor as a reference when calculating an app&#039;s usage.  An app uses CPU to handle requests (in the Python layer) and also when interacting with the datastore.  The actual amount used by an app to handle a given request is highly dependent on what the app actually does.  Apps that do a lot of heave datastore writing and Python-layer processing will use more CPU, while apps that make extensive use of our Memcache API and write sparingly will use less CPU.

I hope this is helpful!]]></description>
		<content:encoded><![CDATA[<p>Great questions.  Our mechanism for metering CPU usage is outlined here:</p>
<p><a href="http://code.google.com/appengine/docs/quotas.html#Requests" rel="nofollow">http://code.google.com/appengine/docs/quotas.html#Requests</a></p>
<p>Essentially, we use a generic 1.2 GHz Intel x86 processor as a reference when calculating an app&#8217;s usage.  An app uses CPU to handle requests (in the Python layer) and also when interacting with the datastore.  The actual amount used by an app to handle a given request is highly dependent on what the app actually does.  Apps that do a lot of heave datastore writing and Python-layer processing will use more CPU, while apps that make extensive use of our Memcache API and write sparingly will use less CPU.</p>
<p>I hope this is helpful!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alistair Croll</title>
		<link>http://gigaom.com/2009/02/24/google-app-engine-announces-pricing/#comment-161966</link>
		<dc:creator><![CDATA[Alistair Croll]]></dc:creator>
		<pubDate>Wed, 25 Feb 2009 02:27:49 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=40633#comment-161966</guid>
		<description><![CDATA[Thanks for the questions -- I&#039;ve asked the guys at Google to chime in and clarify here.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the questions &#8212; I&#8217;ve asked the guys at Google to chime in and clarify here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://gigaom.com/2009/02/24/google-app-engine-announces-pricing/#comment-161965</link>
		<dc:creator><![CDATA[Ryan]]></dc:creator>
		<pubDate>Tue, 24 Feb 2009 21:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=40633#comment-161965</guid>
		<description><![CDATA[@Shion

I have the same question.  Amazon&#039;s EC2 charges for an active cpu.  Its either &quot;on&quot; or &quot;off&quot;, regardless of how much work that CPU is doing.  My impression from the Google AppEngine was that the pricing would be based on cpu cycles expended through handling work/traffic.  So, you could consume fractions of physical CPU&#039;s, and thus not have to start with the $80/month that EC2 demands for a CPU.  I would appreciate an explanation.]]></description>
		<content:encoded><![CDATA[<p>@Shion</p>
<p>I have the same question.  Amazon&#8217;s EC2 charges for an active cpu.  Its either &#8220;on&#8221; or &#8220;off&#8221;, regardless of how much work that CPU is doing.  My impression from the Google AppEngine was that the pricing would be based on cpu cycles expended through handling work/traffic.  So, you could consume fractions of physical CPU&#8217;s, and thus not have to start with the $80/month that EC2 demands for a CPU.  I would appreciate an explanation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shion Deysarkar</title>
		<link>http://gigaom.com/2009/02/24/google-app-engine-announces-pricing/#comment-161964</link>
		<dc:creator><![CDATA[Shion Deysarkar]]></dc:creator>
		<pubDate>Tue, 24 Feb 2009 20:40:43 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=40633#comment-161964</guid>
		<description><![CDATA[Any idea how Google defines a CPU-Hr?  I.e., is it a 2 GHz machine or what?  The FAQ says it&#039;s a megacycle, but that doesn&#039;t really answer the question.]]></description>
		<content:encoded><![CDATA[<p>Any idea how Google defines a CPU-Hr?  I.e., is it a 2 GHz machine or what?  The FAQ says it&#8217;s a megacycle, but that doesn&#8217;t really answer the question.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gee</title>
		<link>http://gigaom.com/2009/02/24/google-app-engine-announces-pricing/#comment-161963</link>
		<dc:creator><![CDATA[Gee]]></dc:creator>
		<pubDate>Tue, 24 Feb 2009 19:34:55 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=40633#comment-161963</guid>
		<description><![CDATA[Any idea when the prices will go into effect?  Didn&#039;t see a link to the formal announcement in the post.]]></description>
		<content:encoded><![CDATA[<p>Any idea when the prices will go into effect?  Didn&#8217;t see a link to the formal announcement in the post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

