Regardless of the cost, it's not documented anywhere or explained why a charge is occurring. It seems rather unfair (and well there are other words for it) to charge users for Always On feature yet still bill them CPU. I would think that paying $0.30 per day for Always On would cover the idle CPU costs but then still try to under the radar charge people for the CPU as well and then when people bring it up in the discussion boards to just ignore it. Well, seems fishy.
On Wed, Mar 2, 2011 at 1:31 PM, Simon Knott <knott.si...@gmail.com> wrote: > I've was thinking about the "charging" of idle instances on my drive home > and have realised that it really doesn't add up to very much - basically, > you end up having ~8mins of idle CPU cost for an entire day, if you have 10 > instances for your app, assuming that the idle CPU_ms cost doesn't fluctuate > and stays on that linear scale. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
