We're still working through the details of reserved instances. The constructive feedback on this thread is useful; it is theoretically possible to pay for an unused instance that requests spill into when they go over capacity of the current spun up requests. That is - pay for one more instance than you need to avoid a loading request - for many people, they would go from 0-1, and for some folks, they would go from 1-2, and so forth.
Even if this isn't the case when we first launch the feature (remember that we are always iterating to improve App Engine), the issue with many of our developers looking for this feature is that they are relatively low QPS applications that experience loading requests on every single request. As a result, a high percentage of their requests take several seconds, and these are the developers we intend on serving with this feature. At the QPS tier where you spin up additional instances to handle load, it is a much lower % - an almost negligible % of requests that take several seconds. While this is far from ideal, we've heard very little feedback from our developers running high QPS (100s - 1000s QPS) applications about this. I suspect it simply has to do with what users have expected with regards to latency spikes with the internet in general and just pass it off. Heck, I refresh pages several times at home sometimes, but that's because my DSL connection is terrible ... and probably also related to the fact that my WiFi router is next to a microwave. I'm not defending it, as in our perfect scenario all requests are served in sub 200ms. Businesses may or may not be willing to pay the cost to deal with these requests. If any of you are running high QPS applications, have these "additional loading requests" affected your business? If these requests have caused measurable loss of revenue or usage, then you'd have to weigh this as well as its opportunity cost against the (still undecided) cost of keeping serving instances ready. On Tue, Mar 30, 2010 at 7:57 AM, Baz <b...@thinkloop.com> wrote: > Shawn, > > By the same token google could cut all their hardware in half and double > page loads, check out this formula: > > NumberOfRequests / HardwareQuality = PageLoad > > Therefore, Google should power the entire GAE infrastructure with a netbook > - yes each page would take 2.5 decades to load, but imagine the cost > savings! > > The main point of my post is the model, not the money. I am more than > willing to pay for AppEngine as I love it and think it's the future. The > issue is that I don't want to pay and manage "instances" because in my > opinion that goes against the model. I would prefer to pay a higher rate (or > the equivalent money some other way) without the knowledge of instances. > > With all that said, and re-reading some other posts, I may actually be > wrong here... To be sure, if I pay for a warmed instance and, say, my site > gradually becomes more and more popular and gradually goes from 1 instance > to 11 - have I received the benefit of a warmed instance at every step of > the way? Is my twelfth instance now the "warm" one? > > Cheers, > Baz > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com<google-appengine-java%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
