Reduce chromaprint peak-scan cost without changing fingerprint output
Constraint: the live FMA smoke is still running, so the optimization had to preserve existing hash semantics rather than adopt the faster non-equivalent peak picker Rejected: maximum_filter-based peak picking | changed peak/hash outputs despite much larger speedup Confidence: high Scope-risk: narrow Directive: Keep future chromaprint optimizations hash-equivalent unless evaluation baselines are intentionally regenerated Tested: compared old vs new peaks and hashes on fma_00000.mp3, measured 2.02x speedup, py_compile passed, rechecked live FMA smoke still in build-index Not-tested: full build-index completion on the live 8000-reference FMA run has not finished yet
Showing
2 changed files
with
36 additions
and
7 deletions
-
Please register or sign in to post a comment