Worker pooling, if per-job font indexing ever shows up in compile_duration_seconds #7
Labels
No labels
deferred
waiting-on-julian
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jlxq0/typst-mcp#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Migrated from
Plan.md's "Deferred (do not drift into these)" section when that file was retired; open work belongs in issues, not in a file with no state. Nothing here is scheduled and no decision has been taken. Do not start it without an explicit go.Every compile runs in a one-shot subprocess that exits after one document. That is not an accident to be optimised away: it is the containment for Typst's
FileIdinterner, a permanently-leaked 16-bit counter that panics at 65 535 distinct paths, and forcomemo's global memo cache. Neither is reclaimable in a long-lived process. Any pooling design must keep a hard ceiling on documents per worker.The trigger is a measurement, not a preference. Open this only when per-job font indexing is visible in
compile_duration_seconds. It is not visible today.Plan.md's wording: "Worker pooling — only if per-job font indexing shows up in
compile_duration_seconds."