* ui: move tools/ui to ui/apps/chat The chat app moves to its own root folder, ui/apps/chat, as the first step of splitting the UI into one library (ui/lib) and the apps built on it (ui/apps). The code is unchanged; every path that pointed at tools/ui now points at ui/apps/chat: CMake adds it from tools/, and the Dockerfiles, the Nix package, the workflows, the labeler, CODEOWNERS, .editorconfig, the git hooks, the dev and demo scripts and the docs follow it. Assisted-by: Claude (Opus 5.5 Medium) * ui: name Llama Chat's package @ggml-org/llama-chat It was still called llama-ui, the name of the library that now sits beside it in ui/lib (@ggml-org/llama-ui). The package stays private; the app's display name and the llama-ui.zip build artifact are unchanged. Assisted-by: Claude (Opus 5.5 Medium) * ui: call the built-in web UI Llama Chat in docs, help text and comments The app in tools/ui is Llama Chat; Llama UI is the component library it is built from. Prose that said "Web UI", "web UI" or "WebUI" for the app now names it: the READMEs, SECURITY.md, the --ui help text, the CMake option description, one server log line, code comments and the Storybook intro. Names that others depend on are unchanged: the deprecated --webui flag aliases, the LLAMA_*_WEBUI CMake and environment names, the webui_settings field, the storage migration keys and the Nix attributes. Assisted-by: Claude (Opus 5.5 Medium) * ui: name tools/ui as a former path of Llama Chat in the code-review skill Changes under the old tools/ui path, as well as tools/server/webui, still get the Llama Chat checklist. Assisted-by: Claude (Opus 5.5 Medium) * ui: name Llama Chat's path in the security policy's exclusions Llama Chat no longer lives under tools/server/, so the exclusion listed under it now names ui/apps/chat. What is covered stays the same. Assisted-by: Claude (Opus 5.5 Medium)
2.7 KiB
Agentic thread perf harness
Two tiers, both reusing the existing vitest projects (see vite.config.ts).
Tier 1 - agentic-stream.perf.svelte.test.ts (project: client, real Chromium)
Mounts ChatMessageAgenticContent and replays a stream, replacing the message
object on each chunk exactly as the real pipeline does:
chat.svelte.tsupdateStreamingUI()runs per SSE chunkconversations.svelte.tsupdateMessageAtIndexdoes{ ...old, ...updates }
That new object identity is the thing under test: it cascades through
deriveAgenticSections (which returns fresh AgenticSection objects) into every
tool-call block in the message, including completed ones.
npx vitest --project=client --run tests/client/agentic-stream.perf.svelte.test.ts
Reading the output
mean/p95/max- the synchronous window per token: prop write,await tick(), then a forcedoffsetHeightread so style and layout are included rather than deferred.sync- sum of those windows. This is the number to optimize.wall- the whole run including workMarkdownContentdefers into its ownrequestAnimationFrame. It carries a ~16.7ms/token idle floor because the harness yields a frame each iteration, so comparewallacross fixtures, never againstsync.
The knobs, and what each one discriminates
The point of the harness is the scaling curve, not any single number.
| Knob | Reads on |
|---|---|
priorToolCalls (0/1/5/20) |
the reactive fan-out. Flat => no fan-out. Linear => confirmed. |
toolResultBytes |
whole-blob string scans (extractSearchResults, parseToolResultWithMedia, classifyToolResult). |
editFileEdits |
computeLineDiff, the O(m*n) LCS. |
openCodeFence |
hljs.highlightAuto on partial code. |
Deliberately no hard assertions: CI timing is noisy and the value here is the before/after delta, not a gate.
Caveat
This measures one message's subtree. In the real app ChatMessages.svelte
rebuilds its whole displayMessages list per token, so multiply by the number
of rendered messages to get the conversation-level cost.
Tier 2 - ../unit/agentic-hotpath.bench.ts (project: unit, node)
Per-call costs for the pure functions the curve implicates.
npx vitest bench --project=unit --run tests/unit/agentic-hotpath.bench.ts