A model's parse is still paid cold in every process; the library record cache does not cover it

Abierto
#2,344 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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

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)

  1. Per-document content hashes on the wire — add content_sha256 to
    SourceDocument (alongside or instead of inline content). 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.
  2. A warm/persistent model cache — a bounded, content-addressed on-disk cache
    of a whole model's analysis (the InterfaceRecord machinery generalised from
    libraries to a project's documents), or a WarmModel RPC that keeps a model
    resident across processes. Bound it by bytes, with eviction, as
    libs.Cache is.

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 same affected answer 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

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Open-MBEE/OpenSysML

Todos los issues de Open-MBEE/OpenSysML

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.