mirror of
https://github.com/bulwarkmail/webmail.git
synced 2026-10-31 08:13:50 +00:00
Linus Rath
e38e326efb
Every plugin iframe loaded /plugin-sandbox, a force-dynamic Next page. Each frame then fetched, parsed and hydrated Next's client router on top of React and the runtime, and the server rendered the page once per frame, one after another when a dozen plugins started together. Sandboxed frames have opaque origins, so the browser's code cache never helps, and they run on the host page's main thread: with 12 plugins the frames took 2.5-3 s to come up after the app had loaded. The sandbox routes now return a small HTML page with the UI kit's stylesheet and the runtime as an ES module, both built ahead of time: - `scripts/build-plugin-sandbox.mjs` bundles the runtime with esbuild and compiles `plugin-kit.css` with the app's Tailwind setup into `public/plugin-sandbox-assets/`, with a manifest. Named Tabler imports are pointed at the icons' own files, so the full icon set stays in a chunk that only loads for an icon name the kit doesn't ship. - `npm run build`, `npm run dev`, the Dockerfile and the perf-guard workflow run it before `next build`. - `lib/plugin-sandbox/sandbox-document.ts` writes the page; proxy.ts still sets the sandbox CSP and the script carries its nonce. - The assets are served from public/ with CORS and immutable caching. A frame on an idle page is ready in 255 ms instead of 362 ms, eleven at once in 1.0 s instead of 2.1 s.
50 lines
1.3 KiB
YAML
50 lines
1.3 KiB
YAML
name: "CI: Perf guard"
|
|
|
|
# Render passes, component renders and JMAP requests per open / search /
|
|
# folder switch, against a production build with the dev mock's
|
|
# benchmark-sized corpus (scripts/perf-guard). Counts, not timings: they do
|
|
# not drift with runner load, so a failure means the code does more work.
|
|
|
|
on:
|
|
push:
|
|
pull_request:
|
|
|
|
# The job builds and runs the checked-out code; a compromised step must not
|
|
# hold a token that can write to the repository.
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
perf-guard:
|
|
name: Perf guard
|
|
runs-on: ubuntu-latest
|
|
timeout-minutes: 30
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v4
|
|
|
|
- name: Setup Node.js
|
|
uses: actions/setup-node@v4
|
|
with:
|
|
node-version: 22
|
|
cache: npm
|
|
|
|
- name: Install dependencies
|
|
run: npm ci
|
|
|
|
- name: Install Playwright browser
|
|
run: npx playwright install --with-deps chromium
|
|
|
|
# The same bundler the Docker image uses, with the dev mock compiled in.
|
|
- name: Build
|
|
env:
|
|
DEV_MOCK_JMAP: "true"
|
|
NEXT_TELEMETRY_DISABLED: "1"
|
|
GIT_COMMIT: ${{ github.sha }}
|
|
run: node scripts/build-plugin-sandbox.mjs && npx next build --webpack
|
|
|
|
- name: Run perf guard
|
|
env:
|
|
CI: "true"
|
|
run: npm run test:perf-guard
|