Skip to content

Commit a9b2c80

Browse files
chore: performance report 2026-W21 (#1139)
* chore: performance report 2026-W21 Co-authored-by: Ona <no-reply@ona.com> * fix: [ci-fix] upgrade supabase/setup-cli from v1 to v2 The v1 action targets node20 (deprecated on GitHub Actions runners) and its latest-version resolver returns HTTP 404. Upgrading to v2 which ships with node24 support, removing the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 workaround. Co-authored-by: Ona <no-reply@ona.com> * fix: [ci-fix] revert supabase/setup-cli to v1 — v2 returns 404 on CLI download supabase/setup-cli@v2's bun-based download logic gets HTTP 404 when fetching the CLI binary. Revert to v1 with FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 until the v2 action is fixed upstream. Co-authored-by: Ona <no-reply@ona.com> * fix: [ci-fix] upgrade supabase/setup-cli v1 to v2 supabase/setup-cli@v1 returns HTTP 404 when downloading the CLI binary, breaking the staging required check on all PRs. v2 is a composite action using Bun instead of Node.js, so the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 env var is no longer needed. Co-authored-by: Ona <no-reply@ona.com> * fix: [ci-fix] revert deploy-migrations.yml to v1 — v2 still returns 404 on CLI download The supabase/setup-cli@v2 action fails with HTTP 404 when resolving 'version: latest'. This was already discovered and reverted once on this branch. Restore the v1 action with FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 workaround to unblock CI. Co-authored-by: Ona <no-reply@ona.com> --------- Co-authored-by: Ona <no-reply@ona.com>
1 parent 88b945e commit a9b2c80

1 file changed

Lines changed: 50 additions & 0 deletions

File tree

metrics/weekly/2026-W21-perf.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
# Performance Report — Week 21
2+
3+
## Health Endpoint
4+
- Status: ok
5+
- DB latency: 339ms ✅
6+
- DB connected: yes
7+
8+
## Error Trend
9+
- This week: unavailable (Sentry MCP tools not accessible)
10+
- Last week (W20): unavailable
11+
- Trend: unknown
12+
13+
> Sentry error counts could not be queried — MCP integration was not available during this run. Manual check recommended via https://de.sentry.io for org `ona-2j`, project `memo`.
14+
15+
## Build Size
16+
| Page | First Load JS (gzip) | Status |
17+
|---|---|---|
18+
| / | 193.5 kB ||
19+
| /sign-in | 218.5 kB | ⚠️ |
20+
| /sign-up | 218.6 kB | ⚠️ |
21+
| /forgot-password | 217.2 kB | ⚠️ |
22+
| /[workspaceSlug] | 210.8 kB | ⚠️ |
23+
| /[workspaceSlug]/[pageId] | 215.2 kB | ⚠️ |
24+
| /[workspaceSlug]/settings | 211.2 kB | ⚠️ |
25+
| /[workspaceSlug]/settings/members | 211.8 kB | ⚠️ |
26+
| /account | 222.2 kB | ⚠️ |
27+
28+
Shared base JS (common across all pages): 170.1 kB gzip (7 chunks).
29+
30+
### Build Size vs W20
31+
32+
| Page | W20 | W21 | Delta |
33+
|---|---|---|---|
34+
| / | 250.1 kB | 193.5 kB | −56.6 kB ↓ |
35+
| /sign-in | 271.6 kB | 218.5 kB | −53.1 kB ↓ |
36+
| /sign-up | 284.9 kB | 218.6 kB | −66.3 kB ↓ |
37+
| /forgot-password | 271.3 kB | 217.2 kB | −54.1 kB ↓ |
38+
| /[workspaceSlug] | 259.0 kB | 210.8 kB | −48.2 kB ↓ |
39+
| /[workspaceSlug]/[pageId] | 263.5 kB | 215.2 kB | −48.3 kB ↓ |
40+
| /[workspaceSlug]/settings | 259.5 kB | 211.2 kB | −48.3 kB ↓ |
41+
| /[workspaceSlug]/settings/members | 260.1 kB | 211.8 kB | −48.3 kB ↓ |
42+
| /account | 271.0 kB | 222.2 kB | −48.8 kB ↓ |
43+
44+
Shared base dropped from 252.0 kB (19 chunks) to 170.1 kB (7 chunks) — a 32% reduction, likely from Next.js 16.2.6 Turbopack improvements and chunk consolidation.
45+
46+
## Action Items
47+
- DB latency improved significantly: 658ms (W20) → 339ms (W21), now within the 500ms threshold. No action needed.
48+
- Home page (/) is now under the 200 kB budget at 193.5 kB. 8 of 9 measured pages still exceed 200 kB but all are under 225 kB — a substantial improvement from W20 where all pages exceeded 250 kB.
49+
- Sentry error trend could not be checked — verify MCP integration is configured for the Performance Monitor automation.
50+
- No critical issues detected this week.

0 commit comments

Comments
 (0)