OK, so we submitted a quota request - even though there is technically no category for dispatch.yaml rules. Thank you for suggesting this! Let's see how this goes, its no less than our 5th (!) attempt to make the Google Cloud division answer our inquiry, which is beyond ridiculous. Just to list what I did:
* Contact the sales form in the Google Cloud console, asking for a quota. Never got a response. * Managed to track down a local GCP representative. Nice guy, but could not answer our request either. * Tried phone support, got almost stuffed up by first-level support, who promised to pass it on. Never heard back. * Posted the question here, thanks for the response Jordan - direct addressing by bypassing dispatch.yaml is unfortunately not an option for us. * Now put in a quota increase request with elaborate justification and all - let's see what happens. I hope someone from GCP reads this and re-thinks their approach. We are dual-using AWS, which is an entirely different experience. More mature, much better documented. Soeren CTO Clipchamp Pty Ltd On Tuesday, August 22, 2017 at 12:12:34 PM UTC+10, Soeren Balko wrote: > > Thanks, Jordan - increasing the limit to 30 would already help a lot for > now. Not sure what causes the memory consumption blow-out, I would have > thought that some glob expressions do not take up much main memory. And as > I said, we are happy to pay for the extra resources you need to provision. > Or use the load balancer service, if it was made available for GAE (it > seems to be limited to your IaaS offerings atm). > > We will explore the direct addressing method, even though I am not fully > clear how this works with custom domains/SSL certificates. > > Soeren > > On Tuesday, August 22, 2017 at 12:51:28 AM UTC+10, Jordan (Cloud Platform > Support) wrote: >> >> With more dispatch rules comes more CPU and memory resource requirements >> per app. Therefore there is indeed a hard limit, but I think it is a bit >> more than 20 (maybe 30?). It is recommended to file a Quota Increase >> Request >> <https://support.google.com/cloud/contact/gae_quota_increase?hl=en>to >> have a conversation with support to gauge the requirements of your >> application and its quota needs. >> >> Ideally it is recommended to design your application to abide by App >> Engine quotas as they are set to protect the overall underlying >> architecture. Treating other micro-services as backend services and >> directly routing requests to them using their full target address >> <https://cloud.google.com/appengine/docs/standard/python/how-requests-are-routed#targeted_routing> >> via >> your main frontend default service is the recommended approach. This way >> you only have to maintain the URL requests to your main frontend >> client-facing default service, and not every service. >> > -- 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 https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/52e03924-bd84-44dd-aadb-9cb0bf216cdd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
