Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

HermitCrab analysis: port the edge-segment prefilter (time-only, 0 steps)

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

I maintainer di solito rispondono entro 1 giorno

@johnml1135 ci sta già lavorando.

Dal 28/10/2026.

  • #574 di @johnml1135 — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
backend

Direzione di ricerca

Read docs/optimizations/edge-segment-prefilter.md and inspect AnalysisAffixProcessRule; then compare the current rules with #561 and #562 if either has landed. Reproduce the archived parity and conformance checks, and run the same-binary A/B measurement on the 45 Sena words and conformance suite. Done means verdicts and trace events match, traversal and arc-check counts are reported, and step count is unchanged; close the issue if the owner rules out time-only work.

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

Descrizione

enhancement Hermit Crab

Port ledger row 22's edge-segment prefilter to master, only if the owner wants a time-only gain. HermitCrab analysis spends 70-91% of its events on attempts that do not unapply; each attempt runs a full FST traversal even when the word's edge segment cannot match. The prefilter makes each attempt cheaper but removes no step, so under the owner's step metric its value is 0.

Problem (steps and cost)

Census: not-unapplied attempts are 70-91% of analysis events. Ledger row 7 ("count is not cost") and row 30 (time-only work is outside the owner's metric) apply. The archived record (origin/perf/hc-optimization-archive, docs/optimizations/edge-segment-prefilter.md) measured parity on 45 Sena words and 464 conformance words, FST traversals -87% and arc checks -54%, trace events unchanged. Steps saved: 0%. Arc checks and traversals are different units and are not steps.

Proposed change

Re-apply the archived prefilter to current master in AnalysisAffixProcessRule (check the first or last segment of the word against the literal edge of the affix pattern before running the traversal). No behaviour change; no new parses.

Soundness

Argued in the archive record; it was sound on the parity sets above. Must be re-argued against current master and against #561 or #562 if they land, since they touch the same rules.

Memory bound

Per-rule edge segment sets sized to the grammar, bytes to KB. No cache.

Expected value (low)

0% in steps by definition. Worth doing only as a wall-time improvement and only if the owner decides time-only work is acceptable. This issue is filed so that decision is recorded, not as a recommendation.

Measurement plan

Same-binary A/B on the 45 Sena words and the conformance suite: verdicts and trace events identical, report traversals and arc checks beside a step count that must not change.

Kill criterion

Close if the owner rules time-only work out of scope (ledger row 30), or if any trace event or parse differs.

Dependencies

None. Interacts with #561 in that it removes whole partial subtrees before their attempts run, which reduces the attempts this prefilter would make cheaper.

Related

  • PR #490: HermitCrab optimization round record (ledger rows cited above are in it).
  • PR #480: HermitCrab conformance suite. Conformance per-fixture verdicts must be identical with and without the change.
  • Units: deterministic analysis events and synthesis steps, never ms. "% less work" = (off - on) / off per grammar, never pooled. Census figures are ceilings unless stated. Ranges marked "est." are estimates that the shadow phase replaces with measurements.
  • Owner constraint: no memo or cache; any new structure must be grammar-sized and at most a few MB.

🤖 Generated with Claude Code

Lingua principale
C#
Stelle
29
Fork
16
Merge medio
6g 13h
PR unite (30g)
12

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

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 sillsdev/machine

Tutte le issue di sillsdev/machine

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.