⚡ Optimize heatmap date parsing performance

[is0692vs]

💡 What: Eliminated new Date() instantiation inside the 300-event limit loop for calculating heatmap values in src/lib/github.ts. Instead, the date part (YYYY-MM-DD) is extracted and mapped to its day of the week using a Map cache. The hour is extracted directly from the standardized ISO string (at indexes 11 and 12) using charCodeAt.

🎯 Why: Creating a new Date object for up to 300 events inside a loop creates unnecessary memory allocation and parsing overhead. While JS handles it reasonably well, directly parsing a known ISO 8601 string format (YYYY-MM-DDTHH:MM:SSZ) is vastly faster and scales better.

📊 Measured Improvement:

• Baseline (new Date() for each event): ~1395 - ~1487 ms (for 10k iterations of 300 events)
• Optimized (Map caching + charCodeAt for hours): ~365 ms (for 10k iterations of 300 events)
• Performance Gain: ~75% faster execution time for this specific code path.

---

PR created automatically by Jules for task 12315538552028124209 started by @is0692vs

[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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
github-user-summary	Ready	Preview, Comment	Mar 20, 2026 7:25am

[coderabbitai]

Warning

Rate limit exceeded

@is0692vs has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 10 minutes and 7 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d07b8c9f-710c-4b3e-9a3f-2895d258d473

📥 Commits

Reviewing files that changed from the base of the PR and between 87d145d and 164f22b.

📒 Files selected for processing (1)

• src/lib/github.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch perf-heatmap-date-parsing-12315538552028124209

📝 Coding Plan

• Generate coding plan for human review comments

---

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 and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the performance of heatmap date parsing by refactoring the event processing loop. It introduces a caching mechanism for day-of-week calculations and utilizes direct string manipulation for hour extraction, thereby minimizing expensive Date object instantiations and leading to a substantial reduction in processing time for activity data.

Highlights

• Date Parsing Optimization: Eliminated new Date() instantiation inside the event processing loop for calculating heatmap values, significantly reducing overhead.
• Day of Week Caching: Implemented a Map cache to store the day of the week for YYYY-MM-DD date parts, preventing redundant Date object creations for the same date.
• Efficient Hour Extraction: Optimized hour extraction by directly parsing the standardized ISO 8601 string using charCodeAt at specific indices, leveraging the known format for speed.
• Performance Improvement: Achieved approximately 75% faster execution time for the heatmap calculation path, reducing processing time from ~1400ms to ~365ms for 10k iterations of 300 events.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a significant performance optimization for date parsing within the activity heatmap calculation. By caching the day-of-the-week lookup and using direct character code manipulation for hour extraction, it effectively avoids costly new Date() instantiations inside a loop. The implementation is solid and achieves the stated performance goals. I have one minor suggestion to improve the readability of the hour extraction logic by removing a magic number.

[is0692vs]

レビュー内容を整理します。

全体所感

• gemini-code-assist: This pull request introduces a significant performance optimization for date parsing within the activity heatmap calculation. By caching the day-of-the-week lookup and using direct character code manipulation for hour extraction, it effectively avoids costly new Date() instant...

主な未解決指摘

• [medium] src/lib/github.ts:678 gemini-code-assist: To improve readability and avoid using a magic number, consider replacing 48 with '0'.charCodeAt(0).

[google-labs-jules]

レビュー内容を整理します。

全体所感

• gemini-code-assist: This pull request introduces a significant performance optimization for date parsing within the activity heatmap calculation. By caching the day-of-the-week lookup and using direct character code manipulation for hour extraction, it effectively avoids costly new Date() instant...

主な未解決指摘

• [medium] src/lib/github.ts:678 gemini-code-assist: To improve readability and avoid using a magic number, consider replacing 48 with '0'.charCodeAt(0).

Good call! I've updated the code to use '0'.charCodeAt(0) instead of the magic number 48 for better readability.