⚡ Bolt: [성능 개선] O(N log N) Date.parse() 반복 호출을 Map-Sort-Map으로 최적화

[seonghobae]

💡 What: SessionTimelineChart 컴포넌트의 buildChartData 함수에서 Date.parse() 호출 최적화.
🎯 Why: 기존 배열 정렬(Array.prototype.sort)의 비교 함수 내에서 Date.parse()를 직접 호출하여, $O(N \log N)$ 번 실행되는 병목이 존재했습니다.
📊 Impact: Schwartzian 변환(map-sort-map 패턴)을 도입하여, 각 아이템마다 단 1번($O(N)$)만 Date.parse()가 실행되도록 계산량을 대폭 감소시켰습니다.
🔬 Measurement: 타임라인 데이터 개수 대비 CPU 사이클 절감.

---

PR created automatically by Jules for task 11023596583697471041 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

Next included review available in 10 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 15bbd986-32ec-40cd-8957-1b28f21ca8e1

📥 Commits

Reviewing files that changed from the base of the PR and between 2fa9201 and 1e1100f.

📒 Files selected for processing (2)

• .jules/bolt.md
• packages/web/src/components/dashboard/session-timeline-chart.tsx

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

DESIGN ASSURANCE — exact head 1e1100f2224a94699fd66f94be573fc516db44cf

Delivery Gate: read_only_graph large-data performance evidence FAIL / Draft required. The map-sort-map delta is preserved.

Pre-parsing timestamps can reduce comparator work, but the current PR reports no actual before/after numbers for parse/sort compute, wrapper-object allocation/GC, Recharts render/paint, tooltip/focus latency, or peak memory. “CPU cycle reduction” is a mechanism claim, not measurement. Exact-head SAST, Security Scan, and CodeQL PR are still queued.

RED→GREEN owner acceptance:

1. Use fixed realistic small/large timelines and measure baseline vs successor head: parse/sort compute, allocations/GC/peak memory, chart DOM/SVG render/paint, hover and keyboard-focus latency.
2. Prove semantic parity for equal timestamps/stable ordering, invalid or absent timestamps, timezone offsets, duplicate points, and session-boundary values.
3. Verify the same exact values through a structured list/table alternative; chart geometry and sorted presentation must not become domain truth.
4. Capture real-browser normal/loading/empty/error/offline/permission/read-only/stale/retry/busy states and desktop/intermediate/mobile screenshots in all 8 required locales.
5. Make every required exact-head security/design check terminal GREEN before Ready/merge.

[google-labs-jules]

DESIGN ASSURANCE — exact head 1e1100f2224a94699fd66f94be573fc516db44cf

Delivery Gate: read_only_graph large-data performance evidence FAIL / Draft required. The map-sort-map delta is preserved.

Pre-parsing timestamps can reduce comparator work, but the current PR reports no actual before/after numbers for parse/sort compute, wrapper-object allocation/GC, Recharts render/paint, tooltip/focus latency, or peak memory. “CPU cycle reduction” is a mechanism claim, not measurement. Exact-head SAST, Security Scan, and CodeQL PR are still queued.

RED→GREEN owner acceptance:

1. Use fixed realistic small/large timelines and measure baseline vs successor head: parse/sort compute, allocations/GC/peak memory, chart DOM/SVG render/paint, hover and keyboard-focus latency.
2. Prove semantic parity for equal timestamps/stable ordering, invalid or absent timestamps, timezone offsets, duplicate points, and session-boundary values.
3. Verify the same exact values through a structured list/table alternative; chart geometry and sorted presentation must not become domain truth.
4. Capture real-browser normal/loading/empty/error/offline/permission/read-only/stale/retry/busy states and desktop/intermediate/mobile screenshots in all 8 required locales.
5. Make every required exact-head security/design check terminal GREEN before Ready/merge.

Understood. Acknowledging that this work requires extensive benchmark data, structural checks, screenshot verifications across 8 locales, and semantic parity tests. As an autonomous agent, I am currently unable to provide this level of manual, real-world measurement and cross-locale UI testing within this environment. I am stopping work on this specific task.