As a side thought, is measuring resource usage itself take too much resource ? ( what percentage of cpu used by google for measuring resource usage of each request ? )
On Feb 11, 12:00 pm, gops <[email protected]> wrote: > We expect Google to maintain price steady for as long as feasible, > whatever it is. > > Google's pricing is always based on resource usage. Moving towards > "MONTHLY" system is not good. > > 1) You may have same pricing structure for FULL TEXT because the > resource usage going to increase anyway ( with extra index scan and > all ) and total billing is going to increase. why separate billing ? > > 2) Same for SQL : CPU usage is going to increase and can be billed. > why separate billing ? > > 3) For, HTTPS, Google is already charging extra for secure requests. > Why separate billing ? > > **Better way to increase profit is to reduce FREE QUOTA for > application.** "Google App Engine" is not public service as Google > Search is. We expect extremely quality ( latency, speed, > availability ) by default from Google ( without paying separately for > it. :P ) > > On Feb 11, 9:56 am, James Broberg <[email protected]> wrote: > > > > > > > > > I'd recommend any/all app developers to go over and have look. I don't > > want to get all worked up on something that hasn't happened yet but > > some of the price points mooted in this survey are positively eye > > watering. I'm happy to put my name to the feedback I left and I'd be > > curious to see what others think. > > > ------------------ > > Honestly, the types of prices you are flagging here are pretty > > concerning, even at the low end, and I can see it becoming > > uneconomical very quickly once you add a few of these services on to > > your account. I'd expect a substantial improvement in performance to > > go along with these prices. > > > It moves well away from the metered billing approach that is used now. > > At the very least I'd like to see some packaging of these advanced > > capabilities at a discount instead of getting nickeled and dimed for > > them individually. > > > As a GAE/J dev, it would lead me to seriously consider porting my app > > to EC2/Beanstalk or other alternatives. When it is more cost effective > > to run 4-5 instances 24/7 on EC2 (even if they are idle half the time) > > than run my app on GAE then your doing it wrong. > > ------------------ > > > -James > > > On 11 February 2011 10:34, Gregory D'alesandre <[email protected]> wrote: > > > > Hello All, > > > I'm one of the Product Managers on App Engine at Google. We are in the > > > process of working on a number of features that you, our users, have been > > > requesting for App Engine but, while this is happening, we wanted to get > > > some additional thoughts and feedback! We've put an anonymous survey > > > together, it is purely voluntary but the information from it will help us > > > make decisions about the future of App Engine. > > > Survey: https://spreadsheets.google.com/a/google.com/viewform?authkey=COPt99s... > > > Thank you all in advance for your time and thoughts! > > > Greg Dalesandre > > > Product Manager, Google App Engine > > > Privacy disclosure: Survey data will be handled in accordance with > > > Google's > > > Privacy Policy > > > <http://www.google.com/intl/en/privacy/privacy-policy.html>. > > > Your email address will not be collected and will not be associated with > > > your survey answers > > > > -- > > > 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.
