{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "performance-docs",
  "title": "Performance",
  "description": "Latest Plate vs Slate large-document benchmark snapshot and how to rerun it locally.",
  "files": [
    {
      "path": "../../content/docs/(guides)/performance.mdx",
      "content": "---\ntitle: Performance\ndescription: Latest Plate vs Slate large-document benchmark snapshot and how to rerun it locally.\n---\n\nPerformance is about whether the editor stays usable when the document gets\nlarge. This page shows the latest 10k Plate vs Slate snapshot from the docs\nbenchmark route and the command that reproduces it locally.\n\n## Latest Snapshot\n\nThis snapshot was captured on June 2, 2026 from the docs benchmark route in\nheadless Chrome. The benchmark uses a 10,000-block document with chunked\nrendering enabled.\n\n| Workload | Slate | Plate core | Plate with basic plugins |\n| --- | ---: | ---: | ---: |\n| Open a mixed document | `524 ms` | `866 ms` | `881 ms` |\n| Type in a mixed document | `26 ms` | `43 ms` | `35 ms` |\n| Open a code-heavy document | `526 ms` | `837 ms` | `1101 ms` |\n\nRead this as a workload snapshot, not as a universal editor score. Mount time,\ntyping latency, plugin cost, and document shape are different performance\nquestions.\n\n## Run The Benchmark\n\nStart the docs app:\n\n<CodeBlockCommand\n  __bunCommand__=\"bun run --filter www dev\"\n  __npmCommand__=\"npm run dev --workspace www\"\n  __pnpmCommand__=\"pnpm --filter www dev\"\n  __yarnCommand__=\"yarn workspace www dev\"\n/>\n\nThen run the public editor benchmark in another terminal:\n\n<CodeBlockCommand\n  __bunCommand__=\"bun run --filter www perf:editor:public\"\n  __npmCommand__=\"npm run perf:editor:public --workspace www\"\n  __pnpmCommand__=\"pnpm --filter www perf:editor:public\"\n  __yarnCommand__=\"yarn workspace www perf:editor:public\"\n/>\n\nThe runner writes a compact JSON summary to\n`apps/www/.tmp/editor-perf-public-summary.json`.\n\n## What It Measures\n\nThe benchmark keeps the public comparison small on purpose:\n\n| Measurement | What it tells you |\n| --- | --- |\n| Opening a mixed document | The cost of mounting a large editor with normal rich-text variety. |\n| Typing in a mixed document | Whether the editor still responds under a large loaded document. |\n| Opening a code-heavy document | The cost of a harder mark-heavy rendering profile. |\n\nPlate core isolates the editor wrapper cost. Plate with basic plugins adds the\ncommon block and mark plugins many editors start with.\n\n## Read The Numbers\n\nCompare like with like:\n\n- use mount numbers for startup cost\n- use typing numbers for interaction cost\n- use the basic plugin column when you care about a real Plate setup\n- rerun the benchmark on your machine before publishing a performance claim\n\nThe raw output also includes lower-level Plate diagnostics, such as node-id\ncost. Those are useful for debugging Plate itself, but they are not the public\nstory.\n\n## Source\n\nUse the [Huge Document](/docs/examples/huge-document) demo for manual\ninspection. The benchmark route lives at `/dev/editor-perf`, and the runner\nlives in `apps/www/scripts/run-editor-perf.mts`.\n",
      "type": "registry:file",
      "target": "content/docs/plate/(guides)/performance.mdx"
    }
  ],
  "type": "registry:file"
}