---
title: "Comment by Julian Neagu on \"Deploying AI Workflows on Cloud Run: Latency, Cold Starts, and Scaling\" | Hashnode"
description: "I’d also keep an eye on rate limits before pushing concurrency too high. It’s easy to make things faster on your side and just move the bottleneck to the model"
url: "https://hashnode.com/posts/deploying-ai-workflows-on-cloud-run-latency-cold-starts-and-scaling/6ac7e695eed20210cedb42bf/comment/6acc83d5823309e9e8dd45fe"
---

[Discussion](https://hashnode.com/posts/deploying-ai-workflows-on-cloud-run-latency-cold-starts-and-scaling/6ac7e695eed20210cedb42bf)

Comment [Deploying AI Workflows on Cloud Run: Latency, Cold Starts, and Scaling](https://hashnode.com/posts/deploying-ai-workflows-on-cloud-run-latency-cold-starts-and-scaling/6ac7e695eed20210cedb42bf)

[Julian Neagu](https://hashnode.com/@julianneagulab)

[Oct 12](https://hashnode.com/posts/deploying-ai-workflows-on-cloud-run-latency-cold-starts-and-scaling/6ac7e695eed20210cedb42bf/comment/6acc83d5823309e9e8dd45fe)

I’d also keep an eye on rate limits before pushing concurrency too high. It’s easy to make things faster on your side and just move the bottleneck to the model API.
