A model's parse is still paid cold in every process; the library record cache does not cover it
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- go
- Área
- backend, performance
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Go
- Estrellas
- 59
- Forks
- 20
- Merge medio
- 10 h 23 min
- PR fusionados (30 d)
- 897
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Open-MBEE/OpenSysML
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 28/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 56/100
Los mantenedores suelen responder en 1 día
Todos los issues de Open-MBEE/OpenSysML
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
krakenhavoc/cmd_and_ctrl#5853 ·
Los mantenedores suelen responder en 1 día
-
flaky test: TestTRTAsyncPrefillFailures/transport reads the token load before prefillDone has released itPosiblemente ocupada @Jackmeson1 la tomó hoy. Abiertoarea/cicd area/gateway kind/misc
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
vllm-project/aibrix#3488 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Type: Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
projectdiscovery/httpx#2735 ·
Los mantenedores suelen responder en 1 día
-
NuGet registry builds every URL from ROOT_URL, ignoring the host the client usedPosiblemente ocupada @gritse la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día