Configure app.yaml for standard env

[Artur Odekov]

Hi, i have deleted env:flex from my .yaml file and deployed to app engine with some other changes in other files. So now im switched to STANDARD env with instance_class F1. 

With this instance class  im not even able to  upload a picture/image to my app, in debugger it show following error Exceeded soft memory limit of 128 MB with 129 MB after servicing 34 requests total. Consider setting a larger instance class in app.yaml. 

Please someone from Google or who know how to configure .yaml file correctly advice me:

1- how do i change instance class,

2- do i need to specify any other parameters like: 

resources:   

cpu: 2   

memory_gb: 2.3   

disk_size_gb: 10

What is the practise ? and one more thing my app has suddenly become so popular, how come ??? im receiving 3000 request per day, how come ? some one is heating my app every 30 seconds ?

[George (Cloud Platform Support)]

Hello Artur, 

You may consider switching to other instance class, such as F2, all depending on your application's needs, and your design decisions. You can not readily refer to practice, all depending on your application. You set instance class in app.yaml. Details are available on the "App Engine Standard Environment" page. 

You may check how come your app has become popular by reading its relevant logs. One has access to logs through Developers' Console. 

A possible explanation for your app's activity might come from side of health checking. The environment verifies periodically that your app is up and running by sending specific requests. You can configure health checking in the app.yaml configuration file. The entry looks similar to: 

health_check:

  enable_health_check: True

  check_interval_sec: 5

  timeout_sec: 4

  unhealthy_threshold: 2

  healthy_threshold: 2

Related to your point 2: you may consider changing mentioned parameters in accordance with your needs. You can establish your app's needs by checking relevant information items from Developers' Console, and set up Stackdriver Monitoring to get even more detail. You can use this information to determine that your app needs more memory or disc size, if usage is proven high for these resources. 

[Artur O]

Hey, thnx a lot for your explanation it makes sense. So does it mean that each health check activates instance? And im being billed for that? For front end  and ram hours?

вт, 22 янв. 2019 г., 21:46 'George (Cloud Platform Support)' via Google App Engine google-a...@googlegroups.com:

--
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.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f07a5099-d3a2-40b8-82bd-f0025c722b52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[George (Cloud Platform Support)]

Google Cloud Platform provides health checking mechanisms that determine whether VM instances respond properly to traffic. To respond to traffic, VM instances need to be existing and running. Health checks are not able to target nonexistent instances, or cause instances to be launched without any other, good reason, and thus cause you extra expense. Default time interval is 5 s for health checks, resulting in an amount of traffic that one does not expected to cause huge cost markups. You can disable health checks, if you consider this advantageous. You may check relevant information in documentation, for instance on the "Creating Health Checks" page.