Hi Paul,

Thanks for including that, this was just to make sure everything was okay, 
just in case.

Since you're using the fully default, I think this behavior is actually 
expected. I would suggest changing a couple of parameters from the default 
to make sure that this behaves properly.

Mainly, you can increase the "min_pending latency", "max_pending_latency" 
and "max_concurrent_request", since the default numbers don't really work 
out for your use case. 

It'll be hard to give you precise numbers since they can vary greatly, but 
I'd definitely look into putting a higher number than the default on these. 
You might need to tweak it over the course of a couple of days to get the 
precise balance of latency/cost you want.

Cheers!

On Friday, July 24, 2015 at 9:57:34 AM UTC-4, Paul Spychala wrote:
>
> version: 2runtime: python27 api_version: 1threadsafe: true handlers: - 
> url: .. lots of handlers- url: /.* script: main_controller.app 
> libraries:- name: webapp2 version: 2.5.2 - name: jinja2 version: 2.6
> There really isn't anything here worth mentioning, its all default
>
>
>
> On Thursday, July 23, 2015 at 6:50:07 PM UTC-4, Patrice (Cloud Platform 
> Support) wrote:
>>
>> Hi Paul,
>>
>> Do you mind including your yaml? The scaling you're using (you say 
>> "default Module settings", but I'd like to make 100% sure about them). It's 
>> possible, with an average of 55,5 ms latency, that the system decided to 
>> spin up a new instance because it didn't want that number to go higher.
>>
>> Automatic scaling does have a tendency to aggressively scale and spin up 
>> instances preventively. You have to understand that it assumes your app to 
>> grow in requests, so if it sees that all of a sudden, an instance receives 
>> 100 requests, the system will assume that your instance will continue to 
>> get MORE (so 100 in a minute means that, in 5 minutes, you'll be receiving 
>> 500 requests a minute), and spins up more instances to accommodate the load.
>>
>> You can read more about this here 
>> <https://cloud.google.com/appengine/docs/python/modules/#Python_Instance_scaling_and_class>,
>>  
>> and with your yaml, I may be able to give you more information as to what 
>> exactly happened, but if you're using the automatic scaling, chances are 
>> this is the culprit here.
>>
>> Cheers!
>>
>> On Thursday, July 23, 2015 at 11:59:12 AM UTC-4, Paul Spychala wrote:
>>>
>>> App Engine ReleaseTotal number of instancesAverage QPS*Average 
>>> Latency*Average 
>>> Memory1.9.242 total9.01055.5 ms64.0 MBytes*Instances *[image: help] 
>>> <https://developers.google.com/appengine/docs/adminconsole/instances>
>>> QPS*Latency*RequestsErrorsAgeMemoryApp Engine ReleaseLogsAvailability
>>> Shutdown0.0000.0 ms2802:52:0156.8 MBytes1.9.24View Logs 
>>> <https://appengine.google.com/logs?app_id=s~scienceslides-hrd&version_id=2.385878376140368174&severity_level_override=1&severity_level=3&filter=instance%3D00c61b117cfc3834f150e0dcaa4720ecc4ce6f11&filter_type=regex&date_type=now&limit=20&view=Search>[image:
>>>  
>>> Dynamic Icon]Dynamic17.71355.5 ms5394314:56:0571.1 MBytes1.9.24View Logs 
>>> <https://appengine.google.com/logs?app_id=s~scienceslides-hrd&version_id=2.385878376140368174&severity_level_override=1&severity_level=3&filter=instance%3D00c61b117c2dd49f502fb8ddf440d37a902d1a7e&filter_type=regex&date_type=now&limit=20&view=Search>[image:
>>>  
>>> Dynamic Icon]Dynamic
>>>
>>> * QPS and latency values are an average over the last minute.
>>>
>>> I get many days where there seems to be a idle Dynamic instance thats 
>>> hardly doing any work thats eatting into my instance-hours. I use the 
>>> default Module settings and don't have anything else customized, so is 
>>> there a good way to check why this happens? I'm fine if an instance starts 
>>> up when traffic spikes however ~28 requests doesn't feel like a traffic 
>>> spike to me.
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/dbe74471-d4b0-4d22-960f-0d3930603222%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to