[google-appengine] Re: New pricing structure infinity increase

2011-11-14 Thread David
You definately have to INCREASE latency to reduce costs. As far as I understood, the sliders work like this: min latency: once it is reached (=a request waits in queue for that time), app engine might start another instance (I don't know on what it bases the decision whether to actually do it) m

[google-appengine] Re: New pricing structure infinity increase

2011-11-14 Thread Kate
But that article says to DECREASE latency whereas the two sliders in the applications seyting page would indicate that you should INCREASE latency. Now I am confused! On Nov 14, 1:34 am, "Gregory D'alesandre" wrote: > Hi Kate, check out the article that we wrote about optimizing your app to > min

Re: [google-appengine] Re: New pricing structure infinity increase

2011-11-13 Thread Gregory D'alesandre
Hi Kate, check out the article that we wrote about optimizing your app to minimize costs: http://code.google.com/appengine/articles/managing-resources.html Without looking at your app its hard to know what the right settings should be although you are only charged for the number of idle instances

[google-appengine] Re: New pricing structure infinity increase

2011-11-13 Thread Kate
I AM getting charged for instances! -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/2ZHYpc8KRU8J. To post to this group, send email to google-appen

[google-appengine] Re: New pricing structure infinity increase

2011-11-13 Thread alex
Mark, in your dashboard, Charts section (top-center of the page), select "Instances" from the drop down box. You should then be seeing "Total, Active, Billed" instances. If you tuned your num of instances down to one, that chart in fact will tell you something like "running: 2, billed: 1" at the

[google-appengine] Re: New pricing structure infinity increase

2011-11-13 Thread Mark Ivey
I'd like to point out that startup latency isn't an issue for all apps. Appengine used to aggressively kill idle instances. When I wrote my app almost every request it served was a startup request. As a result, I optimized for startup latency (used python, avoided django, import almost nothing), an

[google-appengine] Re: New pricing structure infinity increase

2011-11-13 Thread Marcel Manz
Simple answer: unwanted latency I'm also noticing this problem in one of my apps (see my post https://groups.google.com/forum/?hl=en#!topic/google-appengine/dQQ2y01Mbgs) If the scheduler decides to spin up a new instance, this will add unwanted warmup latency to the current request. If you look

[google-appengine] Re: New pricing structure infinity increase

2011-11-13 Thread Mark Ivey
On Nov 13, 11:21 am, Gerald Tan wrote: > Why would you want to stop having 2 instances, when you are only paying for > one? Interesting, only one of those two instances is counting against my instance hours quota? I don't have billing enabled, so my goal is to avoid going over the 28 instance-ho

[google-appengine] Re: New pricing structure infinity increase

2011-11-13 Thread Gerald Tan
Why would you want to stop having 2 instances, when you are only paying for one? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/cxvQuVvsP0UJ. To

[google-appengine] Re: New pricing structure infinity increase

2011-11-13 Thread Mark Ivey
On Nov 13, 7:52 am, Kate wrote: > I cannot work out how to set my instances and latency settings but I > need to do something. > > Until 3 days ago my site cost nothing. Then > 0,42 > 0.33 > 0.37 > 0.86 > 4.80 > > How can this be? I had not altered any settings and I had not uploaded > any new pa