ca821008e2
Measured on a copy of a real 1.2 GB / 253K-event database, 10 simulated browsers + 10 hooks/s for 90 s: event-loop delay p99 1239 ms → 32 ms (max 2.0 s → 94 ms), 266 failed requests → 0, 74 → 111 requests/s served, server RSS 633 → 346 MB. Entry bundle 975 KB raw → 394 KB (106 KB brotli). Server - /api/analytics: the events-table scans run in the read worker (scoped-stats eventAggregates, read-pool job analyticsEvents); runRead takes maxAgeMs — analytics 10 s, /api/workflows 30 s — keyed by the args - /api/workflows/skill-usage: +event_type and a tool_name range instead of LIKE, so it uses idx_events_tool (784 ms → a few ms) - idx_events_session_type_tool (session_id, event_type, tool_name, created_at) replaces idx_events_session_type: covering reads for session stats, the hook dedupes and the import resume point (1.2 s → 20 ms); 64 MB cache_size and 256 MB mmap_size on both connections - WAL: the server sets wal_autocheckpoint = 0 and checkpoints PASSIVE every DASHBOARD_WAL_CHECKPOINT_MS (5 s) from the read worker's own writable connection; a failed checkpoint restores the automatic one (hook COMMIT p95 109 ms → 15 ms at 100 hooks/s) - tmux: one list-sessions answers a whole GET /api/lanes and the heal beat (liveSessions), shared for 1 s and cleared by this process's new/kill — GET /api/run's sync spawns had blocked 60 s of a 90 s run; the heal beat skips tmux when nothing runs; attach options chained into 2 spawns - hooks: TurnDuration/APIError deduped against one read per hook instead of a query per transcript entry (23 ms/hook on a 763-turn session); one lane scan per hook; hourly upserts skip rows that did not grow; frames are sent after the transaction commits (and after the pane binding); new_event carries its row id; a split pane's (slot 1–9) hooks no longer rebind the lane's session_id - watchdog liveness probe runs ps asynchronously; transcript newline scan via indexOf; startup subagent backfill fingerprints the files it already checked - pty attach: backpressure (pause past 1 MB unsent, resume under 256 KB) - static: hashed assets served from their pre-compressed .br/.gz sibling Client - hidden tabs neither refetch on WS events nor poll (useLiveRefresh, panes, lane cards, git header, changes panel, settings); no per-tab hourly /updates/check (the server already checks) - refetch storms throttled (workspace tree/session list 3 s, /api/run only on a run-key change, notification pane lookup only when shown); WS reconnect jitter; terminal retry backoff 1.5 → 30 s, stops on 1008 - heavier throttles for aggregates (15 s) and detail views; Monitor keepIfSame; GET in-flight dedupe in request() - lazy Dashboard/History, xterm (with the first terminal), lane modals, Sagi (only while enabled); only the active locale loads; Workspace chunk prefetched on a /workspace deep link - Sagi: no work while disabled, pupil via CSS variables, memo avatar - build: .br/.gz siblings, sourcemap hidden; service worker no longer caches /assets/ (cache v3 drops the old one) Tests: scripts/test-server.js drops the GIT_DIR-family variables a hook exports, so a suite run from a linked worktree's pre-commit can no longer commit into the real repository or set core.bare. Docs: ARCHITECTURE, DATABASE, API, DEPLOYMENT, client README, docs/plans/perf/README.md (audit, checklist, results).
94 lines
3.3 KiB
JavaScript
94 lines
3.3 KiB
JavaScript
/**
|
|
* @description Service Worker: network-first navigations with an offline fallback, and push
|
|
* notifications. Hashed `/assets/` bundles are left to the HTTP cache (immutable).
|
|
* @author Nguyễn Ngọc Trí Vĩ <vinnt@smartgift.vn>
|
|
*/
|
|
|
|
// Bump this any time the SW logic changes - old clients will install the new
|
|
// SW, drop their existing caches in `activate`, and `skipWaiting` so the
|
|
// freshly-built bundle starts being served on the very next request.
|
|
// v3: drops v2's cache-first `/assets/` entries, which grew with every build
|
|
// and were never pruned.
|
|
const CACHE_NAME = "dashboard-v3";
|
|
|
|
self.addEventListener("install", () => {
|
|
// No pre-cache: network-first below means the cache fills lazily, and
|
|
// there's nothing to "warm" - the v1 SW was pre-caching `/`, which is
|
|
// exactly the file most likely to go stale after a rebuild.
|
|
self.skipWaiting();
|
|
});
|
|
|
|
self.addEventListener("activate", (event) => {
|
|
event.waitUntil(
|
|
caches
|
|
.keys()
|
|
.then((keys) =>
|
|
Promise.all(keys.filter((k) => k !== CACHE_NAME).map((k) => caches.delete(k)))
|
|
)
|
|
.then(() => self.clients.claim())
|
|
);
|
|
});
|
|
|
|
self.addEventListener("fetch", (event) => {
|
|
const { request } = event;
|
|
if (request.method !== "GET") return;
|
|
const url = new URL(request.url);
|
|
if (url.origin !== self.location.origin) return;
|
|
// Skip API, WebSocket, and Vite HMR endpoints
|
|
if (
|
|
url.pathname.startsWith("/api/") ||
|
|
url.pathname.startsWith("/ws") ||
|
|
url.pathname.includes("__vite")
|
|
)
|
|
return;
|
|
|
|
// Hashed bundles under /assets/ are immutable and the server marks them so:
|
|
// the browser's HTTP cache keeps them. Caching them here too only grew a
|
|
// second copy of every build, forever.
|
|
if (url.pathname.startsWith("/assets/")) return;
|
|
|
|
// Everything else (navigations, sw.js, manifest, icons, root /): network-first
|
|
// with cache fallback. The user always gets the freshest UI while online and
|
|
// a sensible fallback when offline.
|
|
event.respondWith(
|
|
fetch(request)
|
|
.then((response) => {
|
|
if (response.ok && response.type === "basic") {
|
|
const clone = response.clone();
|
|
caches.open(CACHE_NAME).then((cache) => cache.put(request, clone));
|
|
}
|
|
return response;
|
|
})
|
|
.catch(() => caches.match(request).then((c) => c || caches.match("/")))
|
|
);
|
|
});
|
|
|
|
// --- Push notifications (existing) ---
|
|
|
|
self.addEventListener("push", (event) => {
|
|
const data = event.data
|
|
? event.data.json()
|
|
: { title: "Agent Monitor", body: "New notification" };
|
|
const { title, ...options } = data;
|
|
event.waitUntil(self.registration.showNotification(title, { silent: false, ...options }));
|
|
});
|
|
|
|
self.addEventListener("notificationclick", (event) => {
|
|
event.notification.close();
|
|
const url = event.notification.data?.url;
|
|
event.waitUntil(
|
|
clients.matchAll({ type: "window" }).then((windowClients) => {
|
|
for (const client of windowClients) {
|
|
if ("focus" in client) {
|
|
// Reuse an already-open tab instead of stacking a new one — that's
|
|
// also why `navigate` (same-origin only) beats postMessage: it works
|
|
// even if the page hasn't wired up a listener for this.
|
|
if (url && "navigate" in client) client.navigate(url).catch(() => {});
|
|
return client.focus();
|
|
}
|
|
}
|
|
if (url && clients.openWindow) return clients.openWindow(url);
|
|
})
|
|
);
|
|
});
|