Free Quoata Reduction?

[conman]

Hi,

I just looked at the dashboard and saw that nearly one third of my
free CPU quoata has been used up for today.

How can that be, because my app didn't do significantly more than the
other day when I looked last (I guess it was end of last week)

Is this a known monitoring issue or was there again a quota adjustment
as in february?

Cheers,
Constantin

[jianwen]

I also noticed that. The free CPU hours now reduce to 6.50 per day,
and Outgoing/Incoming Bandwidth reduce to 1GB per day.

On Jun 23, 2:43 pm, conman <constantin.christm...@googlemail.com>
wrote:

[conman]

Why didn't they send out a notification about that... don't like it to
see that happen, but at least I would like to become informed.

The "free 5 Mio PI" claim from launch last year is now history for
sure - at least for my application.

Cheers,
Constantin

[Sylvain]

It was announced since many months (here and the blog)

http://code.google.com/intl/fr/appengine/docs/quotas.html
http://googleappengine.blogspot.com/2009/02/new-grow-your-app-beyond-free-quotas.html


On 23 juin, 09:30, conman <constantin.christm...@googlemail.com>
wrote:

[conman]

Ah, ok, then this was the reduction that has beeen announced in
februrary.

Tx

On 23 Jun., 10:04, Sylvain <sylvain.viv...@gmail.com> wrote:
> It was announced since many months (here and the blog)
>

> http://code.google.com/intl/fr/appengine/docs/quotas.htmlhttp://googleappengine.blogspot.com/2009/02/new-grow-your-app-beyond-...

[WeatherPhilip]

Actually, I think that this was the timing of the reduction that they
announced in February. I don't think that the size of the quota
reductions (in particular the data reduction) was announced until very
recently. Even then, it was not publicized well (think Arthur Dent and
the 'Beware of Leopard' sign).

According to the post that I read, it said that the levels were set so
that 10% of the existing free apps at 5 million page views per month
would exceed the free quota. How they figured out a page view, I have
no idea. Certainly this will screw up any app that serves up any
significant amount of graphical content.

This new constraint means that a page view has to consume an average
of 6000 bytes or less. [ 10**9 / (5,000,000 / 30) = 6000 ] This is
really tough if a page view contains a dynamically generated image, or
if you are serving an image that is unlikely to be cached on the
user's browser (e.g. a photo gallery app). The 6000 byte limit is OK
if it just covered the html that you need to serve to render the UI.

I would be interested in Google's methodology.

Philip



On Jun 23, 4:34 am, conman <constantin.christm...@googlemail.com>
wrote:

> Ah, ok, then this was the reduction that has beeen announced in
> februrary.
>
> Tx
>
> On 23 Jun., 10:04, Sylvain <sylvain.viv...@gmail.com> wrote:
>
> > It was announced since many months (here and the blog)
>

> >http://code.google.com/intl/fr/appengine/docs/quotas.htmlhttp://googl......

[codingGirl]

Here is a similar discussion in the Google Appengine Python Group:
http://groups.google.com/group/google-appengine-python/browse_thread/thread/226f7959cd54705


The Google appengine team should once and for all state what the
minimum free quotas will be in the next years. Appengine is a total
lock in for our work so Google should be clear what we can expect.