Measure and reduce prefix-query analyzer setup overhead

Aperta
  • Qualcosa non va?
#74 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
nodejs, rust
Ambito
backend, performance

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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)

Lingua principale
Rust
Stelle
3
Fork
0
Merge medio
15h 12m
PR unite (30g)
11

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di HarperFast/fulltext

Tutte le issue di HarperFast/fulltext

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.