Feature Request P2
Status Update
No update yet.
Comments
pv...@google.com
Hello,
Thank you for reaching out to us!
This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs and request features on Google Cloud products. Please go through
I recommend you to
For now, I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.
Thank you!
ku...@gmail.com
Hi,
Thanks for looking into this request and for suggesting an alternative approach!
From the Java docs, it seems that warm-up requests are enabled by default but they still don't prevent loading requests for the first user or for unpredictable traffic patterns.
Min-Idle-Instances setting helps but the problem is that in order to maintain that minimum number of instances in reserve, App Engine frequently keeps starting new instances for new requests turning these requests into loading requests. I have read that increasing the max-pending-latency eases this problem a bit.
With the min-instances setting, I guess there would be a surplus of instances at the start and it would be easier to maintain the reserve specified in the min-idle-instances without directing the users to loading instances.
Please let me know if you think this feature would be worth experimenting with.
Best,
Kunal
Thanks for looking into this request and for suggesting an alternative approach!
From the Java docs, it seems that warm-up requests are enabled by default but they still don't prevent loading requests for the first user or for unpredictable traffic patterns.
Min-Idle-Instances setting helps but the problem is that in order to maintain that minimum number of instances in reserve, App Engine frequently keeps starting new instances for new requests turning these requests into loading requests. I have read that increasing the max-pending-latency eases this problem a bit.
With the min-instances setting, I guess there would be a surplus of instances at the start and it would be easier to maintain the reserve specified in the min-idle-instances without directing the users to loading instances.
Please let me know if you think this feature would be worth experimenting with.
Best,
Kunal
pv...@google.com
Hi Kunal,
It for sure would be! I just wanted to check if you had looked into other possible solutions that could help you while the Feature gets looked at by our back-end team.
In the meantime, I've sent your request up to chain. You should get further updates on this here.
Cheers!
It for sure would be! I just wanted to check if you had looked into other possible solutions that could help you while the Feature gets looked at by our back-end team.
In the meantime, I've sent your request up to chain. You should get further updates on this here.
Cheers!
Description
* This would be particularly useful for low-traffic apps where the first user appears sparingly and most-often sees a loading request
* This setting should also work well together with probably a lower value set for 'min-idle-instances't would mean that some instances are always kept in reserve while some are readily available initially so that users do not see loading requests until a certain minimum amount of traffic