You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4. Configure the service with the appropriate memory limit.
53
53
54
-
You will see as you read through `service.yaml`, that the memory limit has been explicitly
55
-
set to `320Mi` due to container concurrency of `1` with a single `fpm` worker.
54
+
You will see as you read through `service.yaml`, that the memory limit has been explicitly set to `335M`. This leaves ~143M for PHP processes after allocating 192M for opcache.
56
55
See how we got [here](https://cloud.google.com/run/docs/configuring/services/memory-limits#optimizing) and read more about how to [optimize for concurrency](https://cloud.google.com/run/docs/tips/general#optimize_concurrency).
57
56
57
+
**Note:** This sample does not contain extra configuration to tune php-fpm settings to specify the number of workers to correlate with the container concurrency.
58
+
58
59
5. Deploy the multi-container service.
59
60
60
61
From within `service.yaml`, customize the `service.yaml` file with your own project values by replacing
0 commit comments