Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Long codegraph_explore queries are slow on a large index, so the prompt hook times out

Cerrado
  • ¿Algo no está bien?
#2,620 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #2804 de @colbymchenry — fusionado

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
20/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
sqlite, typescript
Área
backend, performance

Línea de trabajo

The proposed fix is already available in commit 1d6f44d on the linked branch, and the issue says it was previously #2621. Review findRelevantContext, the searchNodes and getAllNodeNames paths, and scorePathRelevance; start by comparing that commit with main. The payload names __tests__/explore-term-search-cost.test.ts for coverage; done means the optimizations preserve output and ranking while reducing long-query latency.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

The Claude Code prompt hook times out on long prompts (a pasted log, a skill body): codegraph_explore cost grows with the number of distinct words in the query, and on a large index each word is expensive.

Setup: Linux, v1.6.2 and current main. One index over ~150 Java/Kotlin/TS repos: 19.5k files, 389k nodes, 757k edges, 1.1 GB db.

Cause. findRelevantContext runs searchNodes (FTS, then the LIKE and fuzzy fallbacks) and up to four findNodesByNameSubstring calls per extracted term, with no cap on terms. A 1.7k-char Oracle log gives 132 terms: 1712 SQL calls, 16 s of SQL (v1.6.2, per-statement timing):

statement calls total per call
name LIKE '%x%' (findNodesByNameSubstring) 294 7.3 s 25 ms
searchNodesLike (%x% on name/qualified_name) 78 3.4 s 43 ms
SELECT DISTINCT name (searchNodesFuzzy → getAllNodeNames) 63 3.2 s 51 ms
getDominantFile aggregation 1 1.1 s
FTS 236 0.6 s 2.6 ms

Plus JS: scorePathRelevance re-splits every query word for every scored result (~2.5 s on a 3k-char query).

Fix: commit 1d6f44d on retsamekohC:perf/explore-term-search (was #2621). Output byte-identical to main on all 6 test prompts; __tests__/explore-term-search-cost.test.ts covers the memo invalidation (sync, other connection, rolled-back transaction, rebind) and fuzzy ranking vs a full scan.

  1. FTS joins nodes on the TEXT id; nodes_fts is external-content with content_rowid='rowid', so a rowid join gives the same rows 2.5-3x faster.
  2. getAllNodeNames is documented as cached but is not; memoized per change stamp, like getDominantFile.
  3. Fuzzy fallback only scans names whose length is within maxDist of the query.
  4. scorePathRelevance caches the per-word split.

codegraph prompt-hook, same index copy, ms:

prompt main main + fix
short question 2,540 2,390
Oracle log, 1.7k chars 19,700 14,500
markdown, 3k 46,000 31,300
Java source, 3k 30,300 20,600
markdown, 10k 120,000 72,000
Java source, 10k 69,000 42,000

Not in the fix, your call:

  • The LIKE scans dominate what is left. An in-memory index of distinct lowercased names (one \n-joined string, indexOf per term, ASCII-only case folding to match SQLite LIKE) answers findNodesByNameSubstring in ~2 ms instead of 25 ms with identical rows; qualified_name can be matched on its alphanumeric segments, since a [a-z0-9] term cannot span a separator. Needs invalidation in the long-lived server (the same change stamp would do). With this, a per-process getDominantFile cache on disk, and the PR's changes, v1.6.2 runs the prompts above in 5.5 / 6.7 / 7.0 / 13.4 / 12.9 s. I run this as a --require preload for the hook; happy to turn it into a PR if you want the approach.
  • prompt-hook is a new process per prompt, so the getDominantFile memo never hits there: ~1 s on every prompt on this index.
  • codegraph_explore rejects queries over 10,000 chars, and prompt-hook passes the whole prompt, so a longer prompt silently gets nothing. Truncating in prompt-hook would keep the beginning.
  • Unrelated, noticed on the way: the dominant file of this index is a vendored moment-with-locales.js, so the core-directory boost favors a third-party library.
Lenguaje dominante
C
Estrellas
73.2k
Forks
4.7k
Merge medio
11 h 28 min
PR fusionados (30 d)
596

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 colbymchenry/codegraph

Todos los issues de colbymchenry/codegraph

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.