Please, STOP killing instances after 30s of inactivity (average time
measured, might be even less).
Aren't we paying a minimum 15 minutes startup fee for those started and
killed instances ? May be you could increase this delay to at least 2
minutes ?
These {censored} loading requests make our app totally unusable.
On Wednesday, October 9, 2013 12:33:52 PM UTC+2, Francois Masurel wrote:
>
> Same problem with F2 instances. This f... scheduler is getting us crazy.
>
> There is nothing wrong with starting a new instance but it should wait for
> the instance being properly loaded before redirecting traffic to it.
>
>
>
> On Wednesday, October 9, 2013 12:09:42 PM UTC+2, Francois Masurel wrote:
>>
>> It looks like GAE Java instances don't handle more than 10 concurrent
>> requests.
>>
>> As a result, our GWT app home page which makes about 20 requests needs at
>> least 2 instances loaded to get displayed.
>>
>> And as instances are shutdown very agressivelly (a few seconds), our
>> users are getting hit by these loading requests pretty often.
>>
>> This is making our app totally useless (~10-20s to load a new instance).
>>
>> Is there a way to increase this max number of concurrent requests ?
>>
>> François
>>
>>
>>
>>
>>
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.
