AppEngine performance tuning using idle instances and pending delay settings

I have an application with an application (paid) that averages about 200 visits per day (1000 page views, a periodic number of page views of up to 1000 visits and 10,000 page views, etc.), and I'm currently waking them up through tasks cron every 5 minutes to ensure reasonable performance. This does not always work during application delay bursts (fortunately, this does not happen too often, as recently), and when this happens, my ajax causes a miserable timeout. In addition, the cron-job strategy is not ideal, because it leaves in quotas.

Currently, I have the Idle Instances and Pending Latency settings set to "Automatic".

Does anyone have experience manually tuning these parameters and some typical values ​​that can guarantee the best performance of my application, given the traffic?

+5
source share
1 answer

Instead of setting the cron, simply set the Idle Instances to 1. Idle Instances are instances that are in reserve, giving you an instant response to the increased load. Therefore, if you have a boot that requires three instances, and you set the Idle Instance to one, then you will have 4 instances.

, , . , 28 , ( , , , Idle ).

, Idle Instances, , , , . : , haywire (, ), .

: Idle Instances 1, , .

+2

All Articles