feat(profiling): forward-port P4 baseline export to main (LOC-69)#75
Merged
Conversation
Export the report to the app documents dir as query_profile_<ts>.json/.csv with flush, one PROFILE log line per run, and the export dir/filenames logged for off-device pull (physical-device steps: Xcode Download Container / devicectl). Wire export into the measurement test + add os/os_version metadata. PR-P4.md + README. baseline = embed(ONNX) dominates warm; activate dominates cold.
…-69) Headline correction: the P3/P4 baseline measures latency decomposition only. The LOC-64 recall@10=0.997 is i8-exact-scan vs f32 fidelity (kernel accuracy), NOT the production HNSW-graph e2e hybrid recall (HNSW traverses a dequantized space). Real e2e hybrid recall is unmeasured -> P5/LOC-70 primary target.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
왜 이 PR이 필요한가 (forward-port 구조)
P4(LOC-69) 작업이 main에 도달하지 못했습니다. #73은 GitHub상 MERGED지만 머지 대상이
feat/loc-68-profiler-timing(feature 브랜치)였고, #72가 그보다 먼저feat/loc-68 → main을 머지한 탓에 P4 export 산출물이 main 밖에 고립됐습니다(stacked-merge orphan).git merge-base --is-ancestor origin/feat/loc-69-profiler-export origin/main→ NO.#73은 이미 merged라 reopen/retarget이 불가능하므로,
feat/loc-69-profiler-export → main신규 forward-port PR로 복구합니다. 이 브랜치는origin/main+ 정확히 2커밋(충돌 없음)입니다.포함 커밋
35c121cfeat(profiling): JSON/CSV baseline export + run metadata (LOC-69)afeb9b1docs(perf): clarify baseline is latency-only, not search quality (LOC-69)변경 파일 (4)
example/lib/profiling/profile_export.dart(신규) — baseline JSON/CSV exportexample/integration_test/query_profile_measure_test.dart— export assertion 추가docs/perf/ondevice-query-profiler/PR-P4.md(신규) — P4 결과 저널docs/perf/ondevice-query-profiler/README.md— 상태/헤드라인 정정영향
DESIGN-P5 §5는 "P4가 main에 있어야
feat/loc-70분기"를 전제합니다. 이 PR 머지로 P5 착수 게이트가 정상화됩니다. (#74/P5 스펙은 main 기반 doc-only라 무관.)