From fec3907f83514aa2423b44a2a60bf44fd9d7f33a Mon Sep 17 00:00:00 2001 From: Markus Neusinger <2921697+MarkusNeusinger@users.noreply.github.com> Date: Fri, 11 Sep 2026 22:02:20 +0200 Subject: [PATCH 1/2] docs(performance): frontend row shows one instance, concurrency 80 #11828 and #11829 edited the same infrastructure table row from different branches, so the frontend line still said max-instances=3 / concurrency 15 after both merged. It now matches app/cloudbuild.yaml. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01CELiZYpFBQc5bncjWXYrue --- changelog.d/performance-frontend-row.md | 6 ++++++ docs/reference/performance.md | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) create mode 100644 changelog.d/performance-frontend-row.md diff --git a/changelog.d/performance-frontend-row.md b/changelog.d/performance-frontend-row.md new file mode 100644 index 0000000000..72fe19fe26 --- /dev/null +++ b/changelog.d/performance-frontend-row.md @@ -0,0 +1,6 @@ +### Fixed + +- **`docs/reference/performance.md` shows the frontend at one instance with + concurrency 80.** #11828 and #11829 edited the same infrastructure table row + from different branches, so the frontend line still carried max-instances=3 + and concurrency 15 after both had merged; it now matches `app/cloudbuild.yaml`. diff --git a/docs/reference/performance.md b/docs/reference/performance.md index f4d9c6e037..4c68fbce5c 100644 --- a/docs/reference/performance.md +++ b/docs/reference/performance.md @@ -7,7 +7,7 @@ Backend API response time measurements for anyplot-backend (Cloud Run, europe-we | Component | Config | Notes | |-----------|--------|-------| | Cloud Run (backend) | 1 vCPU, 1Gi RAM, min-instances=1, max-instances=1, concurrency 40 | gen2, startup-cpu-boost=true. Single instance since 2026-09-10: every scale-out was a 9-13 s cold start that a live request paid for (see `api/cloudbuild.yaml`) | -| Cloud Run (frontend) | 1 vCPU, 512Mi RAM, min-instances=0, max-instances=3, concurrency 15 | nginx serving SPA; scales to zero since 2026-08-29, crawler traffic keeps the instance alive | +| Cloud Run (frontend) | 1 vCPU, 512Mi RAM, min-instances=0, max-instances=1, concurrency 80 | nginx serving SPA; scales to zero since 2026-08-29, crawler traffic keeps the instance alive; one instance since 2026-09-11 (see `app/cloudbuild.yaml`) | | Cloud SQL | `db-custom-1-3840`, PostgreSQL 18, PD-SSD 10GB | 1 vCPU, 3.75GB RAM; 3-year commitment until 2029-04-01 | | Cache | In-memory TTLCache, 86400s TTL (24h), max 1000 entries | Per-instance, stampede-protected, stale-while-revalidate | From 3207630e29ff0ce958088303cd3ea5c554700992 Mon Sep 17 00:00:00 2001 From: Markus Neusinger <2921697+MarkusNeusinger@users.noreply.github.com> Date: Fri, 11 Sep 2026 22:06:41 +0200 Subject: [PATCH 2/2] docs(performance): say capped at one instance (Copilot review) --- docs/reference/performance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/performance.md b/docs/reference/performance.md index 4c68fbce5c..e89f2829f2 100644 --- a/docs/reference/performance.md +++ b/docs/reference/performance.md @@ -7,7 +7,7 @@ Backend API response time measurements for anyplot-backend (Cloud Run, europe-we | Component | Config | Notes | |-----------|--------|-------| | Cloud Run (backend) | 1 vCPU, 1Gi RAM, min-instances=1, max-instances=1, concurrency 40 | gen2, startup-cpu-boost=true. Single instance since 2026-09-10: every scale-out was a 9-13 s cold start that a live request paid for (see `api/cloudbuild.yaml`) | -| Cloud Run (frontend) | 1 vCPU, 512Mi RAM, min-instances=0, max-instances=1, concurrency 80 | nginx serving SPA; scales to zero since 2026-08-29, crawler traffic keeps the instance alive; one instance since 2026-09-11 (see `app/cloudbuild.yaml`) | +| Cloud Run (frontend) | 1 vCPU, 512Mi RAM, min-instances=0, max-instances=1, concurrency 80 | nginx serving SPA; scales to zero since 2026-08-29, crawler traffic keeps the instance alive; capped at one instance since 2026-09-11 (see `app/cloudbuild.yaml`) | | Cloud SQL | `db-custom-1-3840`, PostgreSQL 18, PD-SSD 10GB | 1 vCPU, 3.75GB RAM; 3-year commitment until 2029-04-01 | | Cache | In-memory TTLCache, 86400s TTL (24h), max 1000 entries | Per-instance, stampede-protected, stale-while-revalidate |