Skip to content

docs(performance): frontend row shows one instance, concurrency 80 #11830

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MarkusNeusinger merged 2 commits into from
Sep 13, 2026
Merged

docs(performance): frontend row shows one instance, concurrency 80 #11830

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fec3907
docs(performance): frontend row shows one instance, concurrency 80
MarkusNeusinger Sep 11, 2026
3207630
docs(performance): say capped at one instance (Copilot review)
MarkusNeusinger Sep 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions changelog.d/performance-frontend-row.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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`.
2 changes: 1 addition & 1 deletion docs/reference/performance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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; 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 |

Expand Down
Loading