Hi Jason, Yes, Instance Hour billing is based on Total Instances -- turning down 'Max Idle Instances' should be an easy way to reduce your bill. Also, be aware that the way we do real-time monitoring isn't perfect, so the Instances graph or Instances page may show more than the specified number of Idle Instances. However, you will never be charged for more than the number of Max Idle Instances you specify. Give that slider a shot. It will take a few days for the usage report to appear, but if that doesn't have the desired effect on your moola, please contact us at appengine_updated_pric...@google.com and someone will try to help you out personally.
-Alon On Aug 31, 3:39 pm, Jason Collins <jason.a.coll...@gmail.com> wrote: > Alon, > > Today, if I look at the Instances graph, the number of Total Instances > is much higher than the Active Instances (and always has been) - in > our case at the moment: 600 Total to about 150 Active. > > Question: is the sample billing based on the Total Instances? I.e., is > tuning down the Max Idle Instances a really easy cost savings? > > P.S., here are the shocking numbers we're facing: > > app1: 3.8x increase (5.3x increase when Python instances go up in > price, unless we can get to 2.7 and thread-safety in time) > app2: 17.8x increase (34x increase when Python instances go up in > price, unless we can get to 2.7 and thread-safety in time) > > In terms of real $$, for app1, we are looking at going from around > $60,000 / year to around $318,000 / year - that is a LOT of moola for > an application. If we cannot optimize down, it will be a prohibitive > amount of moola. > > j > > On Aug 31, 3:47 pm, "Alon (Google)" <al...@google.com> wrote: > > > > > > > > > Hi All, > > > If your large bill increase is attributable primarily to Frontend > > Instance Hours, one of your best bets is to go to your 'Application > > Settings' page and reduce the value for Max Idle Instances (don't > > forget to click 'Save Settings'). You can use the 'Instances' graph on > > your dashboard to help you to choose a good value -- and you should > > also be able watch the effect on that same graph. > > > -Alon > > > On Aug 31, 2:38 pm, Arnaldo M Pereira <arna...@getwi.com> wrote: > > > > 160% increase in one app for me, 65% in another. > > > > In my case, I don't think it'll be enough to have a comparison table and > > > an > > > optimization doc. I'll make an effort to optimize more my app, but I have > > > the feeling that this has became too expensive for most of my needs now. > > > > On Wed, Aug 31, 2011 at 6:08 PM, Felippe Bueno > > > <felippe.bu...@gmail.com>wrote: > > > > > Greg, > > > > > How could us start using it (reserved instance) before new pricing ? > > > > > I'm asking because I think that what increases the "instance hours" is > > > > the > > > > 15-min startup penalization, am I wrong ? > > > > > On Wed, Aug 31, 2011 at 5:56 PM, Gregory D'alesandre > > > > <gr...@google.com>wrote: > > > > >> Hey Robert, the simplest thing that will reduce your bill will be to > > > >> use > > > >> reserved instance hours. The bill estimates are for full priced > > > >> instance-hours. Are most of the apps java or python? If java, are you > > > >> using concurrent requests? If python, do you want to participate in > > > >> the > > > >> python2.7 trusted tester to try out concurrent requests and give us > > > >> feedback? > > > >>https://docs.google.com/spreadsheet/viewform?formkey=dDVaelk0NkhHMVA2... > > > > >> Thanks! > > > > >> Greg > > > > >> On Wed, Aug 31, 2011 at 1:51 PM, Robert Kluin > > > >> <robert.kl...@gmail.com>wrote: > > > > >>> My apps *are* quite optimized. They are extremely fast, consume, > > > >>> minimal RAM and very little CPU -- but there isn't much I can do about > > > >>> the number of instances used. I consistently see well under 2 QPS / > > > >>> instance -- for requests that always return in under 200ms. Seems > > > >>> like the scheduler is performing quite poorly. > > > > >>> On Wed, Aug 31, 2011 at 15:36, Alon (Google) <al...@google.com> wrote: > > > >>> > Please make sure to look at the strategies outlined in our new > > > >>> > article > > > >>> > to try to optimize your app's resource usage: > > > >>> >http://code.google.com/appengine/articles/managing-resources.html > > > > >>> > On Aug 31, 1:33 pm, Robert Kluin <robert.kl...@gmail.com> wrote: > > > >>> >> Instance hours are the killer here too, seeing between 2x and 4x > > > >>> >> depending on the app (with 50% discount). > > > > >>> >> On Wed, Aug 31, 2011 at 15:28, Waleed Abdulla <wal...@ninua.com> > > > >>> wrote: > > > >>> >> > It's 300% for me (3x what I pay now). Most of the cost is > > > >>> >> > datastore > > > >>> writes > > > >>> >> > and reads, followed by instance hours. > > > > >>> >> > On Wed, Aug 31, 2011 at 1:26 PM, pdknsk <pdk...@googlemail.com> > > > >>> wrote: > > > > >>> >> >> It's an about 50% increase for me, because of datastore writes. > > > > >>> >> >> -- > > > >>> >> >> 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. > > > > >>> > -- > > > >>> > 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. > > > > >> -- > > > >> 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. -- 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.
