⚡ Bolt: [성능 개선] 타임스탬프 파싱 오버헤드 최적화

[seonghobae]

💡 What

타임스탬프 문자열을 밀리초(ms) 단위의 숫자로 변환하는 과정에서 사용되던 new Date(string).getTime() 호출들을 Date.parse(string)로 대체하였습니다.

🎯 Why

new Date(string).getTime()은 파싱 과정에서 내부적으로 Date 객체를 생성(allocation)하게 되어 힙 메모리를 차지하고 가비지 컬렉터(GC)에 부담을 줍니다. 루프 내부나 리액트 컴포넌트의 렌더링 핫 패스(hot path)에서는 이러한 오버헤드가 누적되어 프레임 드랍이나 렌더링 지연을 유발할 수 있습니다. 단순한 밀리초 숫자 값만 필요한 경우 객체를 만들지 않는 Date.parse(string)를 사용하는 것이 훨씬 효율적입니다.

📊 Impact

• 메모리 절약: 렌더링 주기나 데이터 배열 순회 시 임시 Date 객체들이 무수히 생성되는 것을 방지합니다.
• 성능 향상: 객체 할당과 GC 타이밍으로 인한 마이크로 스터터링(미세 끊김)을 예방하여 특히 다량의 이벤트 리스트나 차트 렌더링 시 응답성을 향상시킵니다.

🔬 Measurement

브라우저 DevTools의 Performance 탭(Memory 포함)이나 Node.js 프로파일러를 통해 new Date 호출에 의한 힙 할당(Heap Allocation) 비율이 유의미하게 줄어드는 것을 확인할 수 있습니다.

---

PR created automatically by Jules for task 9058231469180649745 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

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 8 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3215e83a-1b09-45ab-ab05-758f4cf94615

📥 Commits

Reviewing files that changed from the base of the PR and between 085aea3 and 734d85e.

📒 Files selected for processing (4)

• .jules/bolt.md
• packages/web/src/components/dashboard/event-list.tsx
• packages/web/src/components/dashboard/session-timeline-chart.tsx
• packages/web/src/lib/format.ts

---

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