Same Problem Here, as you can see three of the resident instances don't have
any load while
3 dynamic instances take all of the load. This is going to imply a double
cost for us.
https://lh3.googleusercontent.com/-FEFFfaKcPYM/Tl9-NvnFiKI/AAU/nEKXqmyY0R8/gae.jpg
Seems like its a common
This is indeed an issue with showing the comparison bills while always-on is
still running. The Resident instances that you see are the ones that
always-on keeps running. Under the new model if you have a paid app, you
will choose how many instances you want to keep idle at a minimum. So, on
Er, sorry, I meant $1.92 more per day than it should be.
Greg
On Mon, Sep 5, 2011 at 3:50 PM, Gregory D'alesandre gr...@google.comwrote:
This is indeed an issue with showing the comparison bills while always-on
is still running. The Resident instances that you see are the ones that
There seems to be some favoring of dynamic instances taking load over the
always on which is also what I am seeing in my experience. I seem to always
have the 3 resident instances taking no requests while additional dynamic
ones are doing all the work. Could this be exaggerating the price
Yes indeed, you are correct. The new scheduler is geared up for the new
model and as such doesn't use the always on instances as much. So it is
probably 72 instance hours per day higher than it should be.
As long as we are talking about this, someone also reminded me of is that I
haven't been
Same problem, our instances are most of time idle. I think the pricing is
reasonable okay but the scheduler is causing these huge rates.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
We are seeing 600 Total Instances, but only 150 Active Instances (this
application is still set for Automatic Max Idle Instances).
I'm really, really hoping that the sample billing Instance-Hours
computation was made using the Total Instances and that scheduler
improvements combined with the
I had same issue with always-on feature. It had 3 resident instances up
with no traffic and a new request came in and it spun up another instance to
serve the new requests while the resident instances were still idle. My app
only gets heavy traffic on certain days - so not sure if the
