perf: preparse session timeline usage timestamps - #440
Conversation
|
@opencode-agent @cwl-noema-review Review exact current head |
|
Warning Review limit reached
Next review available in: 51 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
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. Comment |
Buyer-visible performance gap
SessionTimelineChartparsed usage timestamps inside the sort comparator, parsed them again during the forward merge, and parsed the samesessionStartedAtanchor once per formatted row. Comparator invocation count is not one-per-record, so long sessions paid repeated string parsing work while the UI thread prepared chart data.Test-first repair
1b7159dce952c662ea5d8a4677760487e479a2c0instrumentsDate.parsethrough the shipped React component and requires each usage timestamp to be parsed exactly once. The prior comparator-based implementation violates that bound.formatRelativeTimeFromMs, parsing the session anchor once per prop value, and asserting the anchor parse budget in the component-level regression.Replacement scope
This clean current-base PR supersedes stale duplicate optimization PRs #432, #434, and #436, plus the still-open narrower PR #425 and duplicate #445. It does not reuse their old heads or reported microbenchmark numbers and does not include unrelated API-route changes from broader predecessor stacks. API-route daily-stat invalidation is owned separately by #446.
Exact-head gate
Current exact head:
f33cefdc7c8c199996e31d7806a76c4005ca27bd.Require exact-head CI, web tests/coverage/build, Security Scan, OSV, dependency review, Semgrep, central OpenCode coverage evidence, current-head automated review, zero unresolved valid findings, and a qualifying independent approval. Do not reuse predecessor-head evidence.