Measure and reduce prefix-query analyzer setup overhead

Abierto
  • ¿Algo no está bien?
#74 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
nodejs, rust
Área
backend, performance

Línea de trabajo

Start with src/engine.rs and trace final_surface_term to understand the analyzer pipeline and final-token length validation. Measure construction, cloning, and request costs in optimized interleaved runs across the listed input types, then compare allocations separately. If reuse is justified, verify the listed behavior, scores, IDs, expansion bounds, and error codes remain unchanged; otherwise retain the current code.

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

Descripción

Outcome

Measure prefix-query analyzer setup cost and reuse a prepared analyzer only if it materially reduces overhead without changing final-token behavior.

Evidence and limits

Code-trace evidence from the reviewed engine: final_surface_term builds the NFKC/possessive/lowercase/ASCII-folding pipeline on each request. The existing surface analyzer also removes long tokens, so blindly reusing it would hide the final-token length error. Allocation and latency benefit are untested. Follow-up from Upgrade fulltext to Tantivy 0.27 with safe index rebuilds.

Acceptance

  • Measure analyzer construction/clone and request cost for short/long, Unicode, prefix and fuzzy-prefix inputs in optimized interleaved runs.
  • If justified, prepare and reuse the exact pipeline through Tantivy TextAnalyzer; retain streaming normalization and final-token length validation before filtering.
  • Preserve completed-term stemming/stop words, possessives, offsets, trailing-whitespace semantics and prefix error codes. Verify scores, IDs and expansion bounds remain unchanged.
  • Report allocation savings separately from end-to-end timings; retain current code if measured savings do not justify extra state.

Parent: Epic: Extend fulltext search capabilities beyond the initial wrapper API.

Priority P3: speculative optimization without a committed roadmap lane or measured regression. Effort Low: one analyzer pipeline and focused parity checks. Task; no milestone, customer context or security incident.

Safe reuse scope in PR72

The safe reuse pass leaves analyzer setup unchanged: native fuzzy-prefix automata are reused, but substituting the existing surface analyzer would change long-token validation. This issue retains the exact-pipeline measurement and parity requirements above; an additional analyzer/cache is not justified without evidence.

Comment generated by kAIle (GPT-6)

Lenguaje dominante
Rust
Estrellas
3
Forks
0
Merge medio
15 h 12 min
PR fusionados (30 d)
11

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 HarperFast/fulltext

Todos los issues de HarperFast/fulltext

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.