Viewing profile — stewart27

I think you can force cold starts between your tests by re-deploying your function/container. You could (optionally) leave a small buffer (<1 minute) after the deployment to ensure…

+1 You can also set up Cloud Scheduler to push to Pub/Sub, which can trigger your function. This is helpful if you don't want your function to be available via a public HTTPS endpo…

Cloud Functions PM here. Your intuition around concurrency is correct: Cloud Functions has "per instance concurrency" of 1. Cloud Run lets you go significantly higher than that (de…

Indeed. If you want to compile the binary yourself/don't want to upload source code, we have a serverless containers product currently available as an early preview (sign up at g.c…

If you're interested in something along the lines of the latter, you can sign up for an early access preview here: g.co/serverlesscontainers

It's definitely something that we've discussed. Would you consider running a container that could be run like Cloud Functions? This container could run the binary that you create. …

> I'm curious how the implementation of Go has affected the ease of integrating other languages. In some ways, it helps. You start to see similar issues arise and know what to look…

While I can't share details publicly, I can confirm that we're actively working on new runtimes and performance improvements.

Which ones would you like to see? We're always looking for new use cases to support.

Cloud Functions PM here. I can give some insight: * We've been running a private early access preview/alpha since last August. * This was our first compiled language on Cloud Funct…

You're not wrong. Cloud Functions Product Manager here. We've been running a private early access preview since we first showed this at GopherCon in August. I'm really happy to see…

The Google Cloud client libraries [1] are fully supported. You can use these to access services like Datastore, Spanner, Natural Language, and many other Cloud services. They work …

Hi optimusclimb -- just want to make clear that using Cloud SQL to connect to PostgreSQL should work using Python 3.7 on the App Engine standard environment. Your earlier comment a…

Yes, Django and Django 2.0 (which only supports Python 3) should work.

Sure, feel free to send it to me directly. stewartr at google.com.

They're both available as early access previews. You can request access via the sign up forms.

Thanks for noticing this. We'll get this updated.

This is supported today! https://cloud.google.com/functions/docs/writing/

You would use Cloud SQL to access PostgreSQL. Here's how you configure your App Engine standard environment project to use Cloud SQL: https://cloud.google.com/appengine/docs/standa…

We're working on suitable replacements for these services. In some cases, e.g., Cloud Tasks, we're pretty close. Others will take a little longer. We'll share updates as we make mo…

I'm not aware of this issue. Can you point me to a public bug/GitHub issue?

There are no changes to the free tier[1] or to apps running using the existing Python 2.7 runtime in the standard environment. [1] You can use the free tier with the new Python 3.7…

Long story short: security is hard. Launching these new unmodified Second Generation runtimes required us to develop new security and isolation technology (based on gVisor [1]). Th…

Yes, this runtime supports arbitrary dependencies specified via a `requirements.txt` file. If you find a library that doesn't work, please let us know. In general, anything that wo…

Hi all, Product Manager for App Engine here. Happy to answer any questions about Python 3 on the App Engine standard environment.