Cloud Run: Right-size market-data service CPU to 1 vCPU - #104

Terraform Plan 📝

No plan file found

Environment: dev
Project: shorted-dev-aba5688f
Image Tag: pr-104

Closing: the premise is inverted, so merging this would do the opposite of what it says.

The PR body reasons that "the deployed service is likely configured with higher CPU" and estimates ~$60/month savings. The IaC says otherwise:

# terraform/modules/market-data/main.tf, on main today
resources {
  limits = {
    cpu    = "0.08"
    memory = "128Mi"
  }
  cpu_idle          = true
  startup_cpu_boost = true
}
...
max_instance_request_concurrency = 1 # Required: cpu < 1 requires concurrency = 1

0.08 vCPU, not something above 1. So cpu = "1" is a 12.5x increase in allocation, described as a right-sizing reduction.

Two further reasons not to take it as-is:

It leaves the concurrency coupling behind. The diff is +1/-1 — CPU only. max_instance_request_concurrency = 1 exists because cpu < 1 forces it. Raise the CPU and that constraint no longer applies, but the setting stays, so each instance still serves one request at a time while provisioning 12.5x the CPU to do it. Whatever the right answer is, these two values are one decision.

Its CI is meaningless. The branch is 840 commits behind main and last ran in July, against a workflow set that has changed since — 4 checks ran here versus 14 on current PRs.

If 0.08 vCPU is genuinely starving the service, that is worth fixing — but on measured latency or throttling, with the concurrency setting revisited at the same time, not on a cost heuristic that misread the current value. Happy to pick that up as a fresh piece of work if it is real.

I could not verify the deployed revision's CPU (no gcloud auth in this session); the above is what the IaC declares.