How will the "Always On" feature figure into the new billing scheme?
I have a very low traffic app that requires the always on feature because otherwise my few users spend a very long time waiting for their requests to be filled. I just was horrified to see that I'll be paying about 7 times as much money to serve my free, non-profit, low traffic, community service app (Tot a Go Go iPhone app) if I use the same model... I'm assuming the increase is because of the three always on instances (the bill for "frontend instance hours" is apparently the killer in the new billing paradigm, according to my horrifying bill projections). Will I be able to just reserve one instance in the future (and maybe only end up with a bill that is twice as high (!?) as it is now? Or can I get a special deal because I'm non-profit? -- 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.
