We experience the same issue with thousands of warmup requests. What is 
going on? Why nobody from google has not replied yet?

On Wednesday, 26 June 2013 17:43:10 UTC+1, Rafael Sanches wrote:
>
> Same here. It's extremely frustrating that the appengine team wasn't 
> capable of making a very simple configuration that would solve many issues 
> with the "crazy scheduler": 
> - Make it possible to spin up JUST one new instance at time. On frontends 
> use the resident instance while that ONE new instance is booting.
> - Only after that ONE instance is up and executing requests, warmup 
> another one (only if necessary, which in 99% of the cases isn't necessary 
> unless you're running an apache bench service). 
>
> This would come very handy in B8 backends for example. Because my java 
> instances take a while to boot, I often find myself with 10 B8 instances 
> warming up. Extremely wasteful.
>
> It would be cheaper for me to hire a fulltime person to be manually 
> pushing the "shutdown instance" button. 
>
> Unfortunately there's no visibility when this extremely simple feature 
> will be done. Till then, let's keep with high costs for things we don't use 
> :)
>
>
> On Wed, Jun 26, 2013 at 9:31 AM, David <turnt...@gmail.com 
> <javascript:>>wrote:
>
>> I am also seeing 3 warm up requests per minute for nearly a day now on my 
>> GAE for Java app.   And often this is happening when there is no incoming 
>> traffic to my app.  My idle instances are also set to 1-1, yet my charged 
>> hours are above this limit.  The dashboard shows up to 8 running instances 
>> at times, with the app being charged for 3 or 4 instances.  The dashboard 
>> also reports that 5% of these warm ups also fail.
>>
>> Will someone from Google please let me know how I can follow up so as not 
>> to be overcharged for this usage?
>>
>> Thanks,
>> David
>>
>>
>>
>> On Tuesday, June 25, 2013 4:49:00 PM UTC-4, chilang wrote:
>>>
>>> Hi,
>>>
>>> I'm seeing 15 warm up requests per secs causing 60+ instances to be spin 
>>> up, despite having little traffic!
>>>
>>> I haven't changed anything (code nor settings) recently. 
>>> This has started in the last 2 hours. 
>>>
>>> I've only noticed this due to app suddenly running out of quota. 
>>> I'm trying to cap Idle Instances to 1-1 to no avail. I've increased the 
>>> quota but at this rate it is going to burn through it very soon.
>>>
>>> Anyone else seeing this ?
>>>
>>> Regards,
>>> Chi Lang
>>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-appengi...@googlegroups.com <javascript:>.
>> To post to this group, send email to 
>> google-a...@googlegroups.com<javascript:>
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to