⚡ Bolt: V8 문자열 파싱 성능 최적화

[seonghobae]

💡 What: new Date().getTime()을 Date.parse()로 교체하고, 정적인 날짜 파싱 계산을 렌더링 루프 외부로 이동했습니다.
🎯 Why: 수백/수천 개의 이벤트가 포함된 가상화 리스트나 차트 렌더링 시 매번 불필요한 Date 객체가 할당되어 메인 스레드를 블로킹하는 성능 문제를 해결하기 위함입니다.
📊 Impact: 객체 생성 오버헤드가 줄어들어 스크롤 및 렌더링 성능이 향상됩니다.
🔬 Measurement: 수천 개의 이벤트가 있는 세션 페이지에서 프로파일러 측정 시 GC 발생 및 파싱 소요 시간이 줄어드는 것을 확인할 수 있습니다.

---

PR created automatically by Jules for task 11952331367038443015 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: 39 seconds

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: 013d72b7-9a75-4eec-a982-afa8a2a8de4b

📥 Commits

Reviewing files that changed from the base of the PR and between 9ef092b and c695f81.

📒 Files selected for processing (3)

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

---

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

[seonghobae]

Closing as superseded by the protected performance lineage plus current focused follow-up #399. Merged #269 already removed repeated sessionStartedAt parsing from EventList with deterministic invalid/pre-session regressions and doctoring; merged #271 replaced the timeline's repeated tool-event scans with a tested forward cursor. #399 is the current-base bounded follow-up for residual timestamp pre-parsing and single-pass array normalization. This stale-base three-file branch therefore no longer provides a unique safe change; its checks/reviews do not transfer.