@Marvin how can I specify container memory size and timeout when deploying to Google Cloud Run

To specify container memory size and timeout when deploying to Google Cloud Run, Prefect documentation does not explicitly mention specific parameters or configuration options for these settings in the context of Prefect 2.x. However, container memory size and timeout are standard settings for Google Cloud Run deployments that can be set using the Google Cloud SDK (

gcloud

) or Google Cloud Console. For

gcloud

, you can specify memory size using the

--memory

flag and set a timeout with the

--timeout

flag when you deploy a service or when you update an existing service. Here is an example of how you might use these flags:

shell
gcloud run deploy SERVICE_NAME --image IMAGE_URL --memory '256Mi' --timeout '300'

In the above command, replace

SERVICE_NAME

with the name of your Cloud Run service, replace

IMAGE_URL

with the URL of your container image, set

--memory

to the desired amount (e.g., 256Mi), and

--timeout

to the desired number of seconds (e.g., 300). For more detailed information and to ensure that you are using the right commands and flags for your specific scenario, it's best to consult the Google Cloud Run documentation: - Setting memory limits - Setting request timeout Remember, these commands and configurations are part of Google Cloud infrastructure management; they may be facilitated by Prefect deployments, but are not specific Prefect features.

@Marvin but how can I set Google Cloud Run max memory from prefect?

The Prefect documentation does not provide explicit instructions for setting the maximum memory of a Google Cloud Run service from within Prefect itself. However, when using Prefect with Google Cloud Run, setting max memory allocation is likely part of the deployment configuration process through the Google Cloud SDK or the Google Cloud Console, rather than an internal Prefect setting. Typically, resource allocation such as memory size would be specified through the gcloud CLI during the deployment of your container to Google Cloud Run, or through Google Cloud Console's GUI when creating or editing a Cloud Run service. Please refer to the Google Cloud Run documentation for detailed steps on setting memory limits, as these settings are part of Google's infrastructure configuration: - Setting memory limits For any further Prefect-specific configuration about work pools or execution environments, you may refer to the Prefect documentation on work pools and managed execution: - Work pools in Prefect - Managed execution in Prefect If these resources still do not provide the information needed, it may be worth reaching out to Prefect's community support or forums for more guidance on this subject.

Found it, configured under work pool settings