Hi Vivek, It's a good point. The most simple advice I'd have for you is to follow this rubric:
(1) If you're unhappy with the cost, reduce max-idle-instances. (2) If you're unhappy with the serving latency and reliability, increase max-idle-instances. I think that's really all that most developers should need to do. There are also lots of optimizations that could made to any app (e.g. concurrency of the runtime or the task queue or the api calls, use memcache, use http caching, use high-replication datastore), and these have always been good things to do, but at a certain point there are diminishing returns on how much can be achieved with these. On Wed, Sep 7, 2011 at 6:21 PM, Vivek Puri <[email protected]> wrote: > Folks, reading all the posts(to be true, i read only the first 10 of > this thread), it seems everyone where is expected to be a GAE billing > expert to survive. Although all the discussions sound interesting, i > dont really have the time to understand all the intricacies, and i > believe same is the case for other developers. Personally, sole reason > for choosing GAE was that i can focus on my business model and not > about balancing set of servers and the billing. It would have been way > better and easier if you had increased the CPU, bandwidth, storage > price to cover up for revenues. If you look at AWS, they have never > done this drastic change in the their service and pricing model. Every > new product comes with its pricing and stackable in some fashion onto > existing products. > > GAE team still has the chance to cancel this change and let everyone > get back to their core job, their application. Please dont make it an > ego issue, if there is still a chance to cancel this change. Just for > comparison, Facebook had cancelled its Facebook Beacon product in 2007 > after putting in tons and tons of effort and partnerships into it. And > as far as i can recall, the amount of resistance to Beacon product was > much less than what i have seen with GAE pricing change. > > -- > 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. > > -- 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.
