A model's parse is still paid cold in every process; the library record cache does not cover it
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- backend, performance
Research direction
Start with workspace/libs/cache.go and the SourceDocument definition and parsing entry points; compare the library record cache with the model parsing path. The issue leaves two possible designs, so first map how base_model_hash and affected work and how TestIncrementalEqualsFresh tests results. Done means a restart or one-document edit avoids redundant parsing while matching a fresh parse, with bounded eviction and safe cache misses.
Written by the indexing model from the issue text.
Description
Disclaimer, this issue was detected and written by an AI
Summary
workspace/libs/cache.go now persists content-addressed IndexRecords for
library documents (name + content hash + set digest + build + format). That
solves the library half of the old ask. The model's own documents are still
parsed cold in every process that opens them: the app, the sysml -render-documents fork and the LSP child each pay the full parse.
Measured on a real 13-document/572 KB set, in-process:
- cold parse ~2.1 s;
- the same sources parsed again in the same process: ~3 ms (the service's
source cache); - a one-document edit restarts at ~2 s, even with
base_model_hash.
SourceDocument carries only file_path/content/language/name; there is
no content hash for an unchanged document and no warm RPC.
Proposal (pick one, or both)
- Per-document content hashes on the wire — add
content_sha256to
SourceDocument(alongside or instead of inlinecontent). A client that
holds the model sends hashes for unchanged documents; the service re-reads
only the changed ones and answers from its content-addressed store. This is
the smallest change that makes edits cheap. - A warm/persistent model cache — a bounded, content-addressed on-disk cache
of a whole model's analysis (theInterfaceRecordmachinery generalised from
libraries to a project's documents), or aWarmModelRPC that keeps a model
resident across processes. Bound it by bytes, with eviction, as
libs.Cacheis.
Keep the existing base_model_hash/affected semantics: a document the service
cannot prove unchanged is affected and re-analyzed.
Tests
- A two-document model: a hash-only re-parse of unchanged content answers the
same model hash without re-analysis (the sameaffectedanswer as a fresh
parse). - A one-document edit sends one new content and one hash; only that document and
its dependents are analyzed; the answer equals a fresh parse
(TestIncrementalEqualsFresh's pattern). - Cache eviction and a missing/corrupt entry fall back to a fresh parse.
- A hash that does not match the content is
INVALID_ARGUMENT.
Acceptance
- A restarting process can open an unchanged model without re-parsing it, or
a one-document edit re-parses only the changed document. - The result always equals a fresh parse; no stale analysis is served.
- The cache is bounded and evictable; a miss is safe.
- Dominant language
- Go
- Stars
- 59
- Forks
- 20
- Avg merge
- 10h 23m
- Merged PRs (30d)
- 897
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Open-MBEE/OpenSysML
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
All issues in Open-MBEE/OpenSysML
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
krakenhavoc/cmd_and_ctrl#5853 ·
Maintainers usually reply within 1 day
-
flaky test: TestTRTAsyncPrefillFailures/transport reads the token load before prefillDone has released itPossibly taken @Jackmeson1 claimed this today. Openarea/cicd area/gateway kind/misc
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
vllm-project/aibrix#3488 · 2 comments ·
Maintainers usually reply within 1 day
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
projectdiscovery/httpx#2735 ·
Maintainers usually reply within 1 day
-
NuGet registry builds every URL from ROOT_URL, ignoring the host the client usedPossibly taken @gritse claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day