It looks like we are being charged at the higher rate of 30-35 instance hours / hour even though only ~10 are active at a time and max-idle is set to 5. Although it's still hard to tell as we're behind ~5 days in billing history summaries.
Is the current scheduler going to be changed before new-billing is implemented? Seems like a must. On Sep 1, 4:48 pm, Millisecond <[email protected]> wrote: > The table at the top of the dashboard is showing 23 active instances, > QPS of 2.6 and a latency of 481ms. Which makes some sense as I'm > hovering between 40 and 80 QPS overall. > > I've set the scheduler to have max 5 idle instances and the min > latency to 60ms, but when I pull down the graph to the "Instances" > display, it has me hovering between ~5 and ~12 active and 30-35 > total. > > Is the graph just not accurate and we're billed for what's in the text > area? Are we charged for active instances or total instances or > instances in the text area? Why isn't it more-or-less "active + 5 as > max = total"? > > With a 3-4 day delay on my billing history reporting, this is going to > be very hard to tweak if I can't see correct numbers on the dashboard. -- 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.
