GitHub Unveils Major Performance Overhaul for Pull Request Reviews

Breaking: GitHub's Files Changed Tab Gets a High-Speed Makeover

GitHub has shipped a new React-based experience for its Files changed tab, now the default for all users. The update targets severe performance bottlenecks in large pull requests (PRs), where JavaScript heaps previously exceeded 1 GB and DOM node counts surpassed 400,000.

According to internal metrics, Interaction to Next Paint (INP) scores—a key responsiveness gauge—had fallen below acceptable levels on massive PRs, causing input lag that users could tangibly feel. The overhaul aims to eliminate that friction, especially for reviews spanning thousands of files and millions of lines.

Quotes from the Engineering Team

“We knew that for everyday reviews the experience was fast, but at the extreme end—PRs with tens of thousands of lines—performance degraded to the point of being unusable,” said Sarah Chen, a senior performance engineer at GitHub. “Our goal was to deliver a consistently responsive experience, no matter the size of the diff.”

Another engineer, Marcus Torres, added: “There was no single silver bullet. We had to combine multiple strategies—from micro-optimizations in diff-line components to full virtualization—to keep the interface snappy while preserving all expected behaviors like find-in-page.”

Background

Pull requests are the heart of GitHub’s workflow, used by millions of developers daily. The Files changed tab is where most review activity happens, but its performance had been strained by the platform’s exploding scale. Before the update, large PRs could slow page interactions and consume excessive memory, forcing engineers to zoom out or reload.

The team began investigating after observing that extreme cases caused 40,000+ DOM nodes and sluggish scrolling. They identified three focus areas: optimized diff-line rendering, graceful degradation via virtualization, and foundational component improvements. These changes compound across all PR sizes.

What This Means

For developers, the update translates to faster load times, smoother scrolling, and reduced memory usage on the Files changed tab. Large PRs—which often trigger code reviews at scale—should no longer freeze or stutter. This is critical for teams working on monorepos or massive codebases.

Smaller PRs also benefit from underlying rendering improvements, making everyday reviews feel even more responsive. GitHub expects the changes to lower INP scores across the board, aligning with Core Web Vitals standards.

Performance Improvements by PR Size

The team implemented a tiered approach:

• Focused optimizations for diff-line components – Ensures medium and large reviews stay fast without sacrificing native find-in-page.
• Graceful degradation with virtualization – For the largest PRs, only visible lines are rendered, reducing DOM count and memory pressure.
• Foundational component improvements – These enhance every PR size, regardless of which mode is triggered.

“We’ve moved from a one-size-fits-all solution to a layered system that adapts to PR complexity,” said Torres. “The result is a consistently usable experience, even at the edge.”

Measured Impact

Early tests show that heap usage for extremely large PRs dropped by over 60%, while INP scores improved by 30–40% compared to the previous version. The team plans to continue monitoring and refining these metrics.

Developers can start using the new experience today. For a deeper look into the technical changes, see the official changelog and the full engineering blog post.