[google-appengine] Re: Understanding 'Frontend Instance Hours'

Take a look at https://developers.google.com/appengine/articles/managing-resources if you haven't already On Wednesday, 25 April 2012 10:51:09 UTC+5:30, Uman Lata wrote: > > I also experience the same problem in my > website. > When this thing happen I observe th

[google-appengine] Re: Understanding 'Frontend Instance Hours'

I had a look at the GAE document for frontend instance but not really know how it works. My application currently only does cron jobs and push queue task. Both uses URL fetch. But all this are still within limits (< 5%). My frontend instance is almost 80%. Correct me if i'm wrong. The quota of

[google-appengine] Re: Understanding 'Frontend Instance Hours'

I also experience the same problem in my website. When this thing happen I observe there is large number of request in the log in small time. So if your app is initiated at burst then this may happen. You can check logs in appengine logs and you can find requests at

[google-appengine] Re: Understanding 'Frontend Instance Hours'

Be sure you do not have something that is periodically creating a burst of tasks into a task queue. I believe the scheduler responds to this by thinking, "Wow. I've got a lot of tasks to clear as soon as possible." This could be very detrimental to your instance counts as you may get a burst of ins

Re: [google-appengine] Re: Understanding 'Frontend Instance Hours'

On Thu, Dec 22, 2011 at 7:36 PM, KK wrote: > Thanks every one for the responses. > > Since it is going to be at least 24 frontend instance hours in a day if > there is steady traffic to my app. What are the guidelines I can follow in > my app to reduce the number of frontend isntance hours above 2

Re: [google-appengine] Re: Understanding 'Frontend Instance Hours'

Thanks every one for the responses. Since it is going to be at least 24 frontend instance hours in a day if there is steady traffic to my app. What are the guidelines I can follow in my app to reduce the number of frontend isntance hours above 24? Would things like setting setting cache header

Re: [google-appengine] Re: Understanding 'Frontend Instance Hours'

Yes. An instance is kept there ready to server traffic, so it costs Google money - so it costs you too. But of course that 24 hours (plus the extra 4) is free. On Thu, Dec 22, 2011 at 7:15 PM, KK wrote: > That's interesting. > > So, if my app just prints "Welcome!" and does nothing else. And if

[google-appengine] Re: Understanding 'Frontend Instance Hours'

Yes. So in this case I'd even recommend setting min idle instance to 1 too So that the "Welcome!" message doesn't need to wait for an instance to warmup before appearing -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussi

RE: [google-appengine] Re: Understanding 'Frontend Instance Hours'

: google-appengine@googlegroups.com Subject: [google-appengine] Re: Understanding 'Frontend Instance Hours' That's interesting. So, if my app just prints "Welcome!" and does nothing else. And if there is a request every 15mins., the front-end instance hours will be

[google-appengine] Re: Understanding 'Frontend Instance Hours'

That's interesting. So, if my app just prints "Welcome!" and does nothing else. And if there is a request every 15mins., the front-end instance hours will be 24 at the end of the day? Thanks Krishna -- You received this message because you are subscribed to the Google Groups "Google App Eng

[google-appengine] Re: Understanding 'Frontend Instance Hours'

There's no way to make sure that your app uses only one instance. Setting max idle instance ensures that you will be changed for a maximum of 1 idle instance. If traffic goes up, the the scheduler may spin up extra instances, however you are only charged for "Max Idle Instance + Active Instance

[google-appengine] Re: Understanding 'Frontend Instance Hours'

Thanks for your reply. So, you mean 4 requests per hour that are perfectly spread out can cause 1 instance hour. Right? So, if I only have ONE instance all the time, it would only mean 24 instance hours in a day and I would never exceed the quota. How do I make sure that my app only uses one in

[google-appengine] Re: Understanding 'Frontend Instance Hours'

Hi, If an instance is spun up, then you will use up 15mins of Frontend instance hours automatically for spinning up the instance. So if those 200 requests are fairly spread out over the 18 hours then it's more than possible to use 50% of your quota. See http://code.google.com/appengine/kb/bi