feat(harness): SessionStart stage timing instrumentation (#897 step 1) - #991
Merged
Conversation
seoseo-ai
approved these changes
Aug 6, 2026
seoseo-ai
left a comment
Collaborator
There was a problem hiding this comment.
Approved after explicit operator authorization using the local seoseo-ai credential.
load-memory.sh now appends one body-free JSON line per run (fixed stage names + integer ms + total) to $CCC_STATE_DIR/memory-timing.jsonl. This validates the issue's static hypotheses — the serial local/recent/shared/ legacy search chain (up to 9s worst case) and the over-split render pipeline — against real fleet data before step 2 (parallel search) and step 3 (unified render) land. Default on, CCC_MEMORY_TIMING=0 opts out; the log self-bounds at ~256KiB; timing never touches stdout or the hook contract.
jinon86
force-pushed
the
feat/897-memory-timing
branch
from
August 6, 2026 13:01
bf9827e to
d300685
Compare
seoseo-ai
approved these changes
Aug 6, 2026
seoseo-ai
left a comment
Collaborator
There was a problem hiding this comment.
Approved after explicit operator authorization using the local seoseo-ai credential.
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
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.
#897 1단계 — 계측 선행
이슈 본문의 순서 고정 지시(① 계측 → ② 검색 병렬화 → ③ 통합 렌더 → ④ setup.sh)에 따른 첫 PR입니다. 최적화 전에 정적 가설을 실측으로 검증합니다.
변경
load-memory.sh가 실행마다 body-free JSON 1행을$CCC_STATE_DIR/memory-timing.jsonl에 추가합니다:{"ts":"…","event":"SessionStart","total_ms":817,"stages":{"sources":2,"dynamic_budget":38,"search_local":501,"dedup":…}}CCC_MEMORY_TIMING=0옵트아웃검증
후속 (이 PR 범위 밖)
2단계(검색 병렬화/3초 전역 예산)·3단계(memory_render.py 통합)는 이 계측 데이터가 쌓인 뒤 진행. nunchi stale 비동기화는 #893, statusline은 #894 소유.