Hey Rori,

I don't want you to drop GAE for many reasons too :)  This bug won't affect
actual billing but rather the current comparison bills.  We are working on a
fix right now and once we have something worth talking about we'll let
everyone know.

Greg

On Wed, Sep 7, 2011 at 2:59 PM, Rori Stumpf <[email protected]> wrote:

>
> I'm *really* hoping you can figure something out. I really don't want
> to drop GAE for many reasons, but I won't have much choice if I'm
> forced to pay for 3 "always on" instances that are not needed. If my
> new app gets enough users then it will make complete sense from a cost
> standpoint, not to mention all the other advantages of the platform.
> But what about my costs while I am building the customer base...
> should I find some other solution that will smooth out the cost curve?
> (and most likely end up staying there).
>
> Of course, if the spin-up's were more predictable, then I could live
> with that and would not need "always on". But my current app needs to
> (preferably) respond within 2 secs. And 1 instance would be just fine
> for that.
>
> Also, as I mentioned before, I think many GAE users (including myself)
> would prefer affordable pricing for low volume apps, as that
> encourages experimentation and proof-of-concept testing on the
> platform. In turn, that should translate into much broader adoption of
> the GAE platform.
>
> Doesn't Google want to lock startups into GAE at the embryonic (i.e.
> no money, just an idea) stage? ;-)
>
>
>
> On Sep 6, 11:45 pm, "Gregory D'alesandre" <[email protected]> wrote:
> > I think we've tracked the bug down.  We are currently treating Always-On
> as
> > if it is 3 min idle instances.  When you try to set Max Idle instances to
> > less than 3 (which wouldn't make much sense if you had known you had set
> min
> > idle instances to 3), the Admin Console doesn't let you and
> (unfortunately)
> > doesn't give a good error as to why.  So, you can set it to 3, but as
> long
> > as Always-On is still on it won't let you set it to less than that.
> >
> > We'll see if we can figure out a way around this...
> >
> > Sorry about that!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to