mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-21 16:18:55 +00:00
d1c455acf7
Replaces the dozen ad-hoc measure-*/profile-* scripts (each reinventing the CDP client — 4 different copies — plus its own arg parsing, stats, output path, and none with a baseline) with one framework under scripts/perf/: - lib/cdp.mjs one CDP client + target discovery + typing + CPU-profile wrapper + DOM selectors - lib/stats.mjs percentiles, histograms, CPU-profile self-time ranking - lib/baseline.mjs load/compare/update baseline + regression gate (new capability) - lib/launch.mjs attach, OR spawn a fully ISOLATED instance - scenarios/* one module per measurement, registered in scenarios/index.mjs - run.mjs / serve.mjs, baseline.json, README.md Isolation solves the long-standing measurement blocker: a running `hgui` held the Electron single-instance lock, so a second instance quit. `--spawn` / `perf:serve` launch with their own --user-data-dir (separate lock scope), their own HERMES_HOME (separate backend/sessions, config seeded from ~/.hermes so it reaches a chat view without onboarding), and their own --remote-debugging-port. Synthetic scenarios drive $messages via window.__PERF_DRIVE__, so no LLM credits. Scenario -> sunset script mapping: stream <- measure-synthetic-stream, profile-synth-stream, profile-long-stream stream --real <- measure-real-stream, profile-real-stream keystroke <- measure-latency, profile-typing, leak-typing transcript <- (new: long-transcript mount cost) submit <- measure-submit, measure-jump session-switch <- profile-session-switch profile-switch <- measure-profile-switch CPU profiling is now a cross-cutting --cpuprofile flag, not 5 separate scripts. CI-tier scenarios (stream, keystroke, transcript) need no backend/credits and are gated against baseline.json (seed values; re-capture with --update-baseline on a reference device). Backend-tier scenarios are report-only. perf-probe.tsx gains loadTranscript() for the transcript scenario. No core files touched; isolation is via CLI args, not env-gated app changes. Verified: node --check all modules, tsc, eslint, and a unit smoke of the stats + regression-gate logic. The end-to-end GUI run (which opens a window) is left to run interactively via `npm run perf -- --spawn`.
40 lines
1.2 KiB
JavaScript
40 lines
1.2 KiB
JavaScript
// Launch a standalone, fully isolated perf instance and leave it running so you
|
|
// can attach the harness (`npm run perf`) or DevTools to it. Ctrl-C tears it
|
|
// down and removes its temp dirs.
|
|
//
|
|
// npm run perf:serve # :9222, temp HERMES_HOME + user-data-dir
|
|
// PERF_PORT=9333 npm run perf:serve # custom CDP port
|
|
//
|
|
// This is the isolation seam: because it uses its own --user-data-dir the
|
|
// Electron single-instance lock never collides with a running `hgui`.
|
|
|
|
import { startIsolatedInstance } from './lib/launch.mjs'
|
|
|
|
const port = Number(process.env.PERF_PORT ?? 9222)
|
|
const devPort = Number(process.env.PERF_DEV_PORT ?? 5174)
|
|
|
|
console.log(`[perf:serve] starting isolated instance (CDP :${port}, dev :${devPort})…`)
|
|
|
|
const instance = await startIsolatedInstance({
|
|
port,
|
|
devPort,
|
|
hermesHome: process.env.PERF_HERMES_HOME,
|
|
userDataDir: process.env.PERF_USER_DATA
|
|
})
|
|
|
|
console.log(`[perf:serve] READY — attach with: npm run perf -- --port ${port}`)
|
|
|
|
let closing = false
|
|
const shutdown = () => {
|
|
if (closing) {
|
|
return
|
|
}
|
|
|
|
closing = true
|
|
console.log('\n[perf:serve] tearing down…')
|
|
instance.teardown()
|
|
process.exit(0)
|
|
}
|
|
|
|
process.on('SIGINT', shutdown)
|
|
process.on('SIGTERM', shutdown)
|