How to use Cloud Run 'always-on' CPU allocation for background work

preview_player
Показать описание

In this episode of Serverless Expeditions, Martin and Wesley optimize their weather alerting app by pulling the values from a cache instead of hitting an external API. Watch as they speed up their app by taking advantage of Cloud Run's "always-on" CPU allocation, allowing them to keep the cache updated and drop app latency by more than 80%!

Chapters:
0:00 - Intro
0:52 - Caching layer
2:04 - Enabling "always-on" CPU & code preview
2:38 - App deploy & demo
3:15 - Cost & autoscaling considerations
4:13 - Summary

#ServerlessExpeditions​ #ServerlessExpeditionsExtended #CloudRun

product: Cloud - Serverless Computing - Cloud Run; fullname: Wesley Chun, Martin Omander;
Рекомендации по теме
Комментарии
Автор

Thank you for this video. I am using Google Cloud at my job and this is something that will be useful to test.

MrSebhtml
Автор

Guys! Hello!

I need my cloud run container work always to permanently collect data of live events. But it seems my cloud run containers are just dying silently after some time. Is there a way to make my func work without timeouts and requests?

AarondovMALKIN
Автор

Would executing background tasks that might take up to 20 - 30 minutes to complete with always allocated CPU keep the instance on until the background task is complete and shut it down once it's done?

zfsboro
Автор

My batch processing runs for 2 hours..will cpu always allocation increase request timeout also

rajanjoshi
Автор

Cronjob + curl on always free compute engine instance, or cloud scheduler...

kamarton