Update on datastore performance

[Ikai L (Google)]

Hey guys,

I just wanted to highlight a new blog post that we've posted about the recent datastore issues:

http://googleappengine.blogspot.com/2010/06/datastore-performance-growing-pains.html

We're still hard at work on the latency problems many developers have been experiencing, but in the meantime, we won't be billing for datastore CPU or storage issues until we have these issues resolved. There are more details in the blog post.

We're still planning on publishing a post-mortem about the most recent unplanned outage, so stay on the lookout for that as well.

--
Ikai Lan 
Developer Programs Engineer, Google App Engine

Blog: http://googleappengine.blogspot.com 

Twitter: http://twitter.com/app_engine

Reddit: http://www.reddit.com/r/appengine

[Ikai L (Google)]

Just a quick clarification: the billing changes only apply to datastore CPU. Storage billing will not be modified.

[hawkett]

I can appreciate the hassle that these issues are causing (me too),
but I was thinking as I read the blog post that I appreciated the
candour. App engine has always struck me as a pretty amazing public
offering, with some fairly significant technical hurdles that I doubt
anyone else would consider taking on. If you consider that google is
attempting to offer infinite scalability to near enough an infinite
number of apps - perhaps app engine is currently proving that, in
fact, infinity^2 *is* more than infinity :)

On Jun 3, 3:22 am, "Ikai L (Google)" <ika...@google.com> wrote:
> Just a quick clarification: the billing changes only apply to datastore CPU.
> Storage billing will not be modified.
>
> On Wed, Jun 2, 2010 at 5:10 PM, Ikai L (Google) <ika...@google.com> wrote:
>
>
>
>
>
> > Hey guys,
>
> > I just wanted to highlight a new blog post that we've posted about the
> > recent datastore issues:
>

> >http://googleappengine.blogspot.com/2010/06/datastore-performance-gro...
>
> > <http://googleappengine.blogspot.com/2010/06/datastore-performance-gro...>We're