Linus Torvalds on why Git had to be fast: The performance story

GitHubAbout 1 min readJun 29, 2025Watch original
THE SUMMARYAI-generated

Key Concepts:

  • Source Control Management (SCM)
  • Performance
  • Patch Application
  • Scalability
  • Quality of Life

Disdain for Existing Source Control Management Projects:

The speaker expresses a strong dislike for most existing Source Control Management (SCM) projects. This disdain stemmed from a desire to improve upon the status quo, rather than simply maintaining it.

Performance as a Primary Motivation:

The biggest issue driving the speaker's dissatisfaction was performance. Specifically, the speed at which patches could be applied to the codebase.

Patch Application and Quality of Life:

The speaker emphasizes the importance of rapid patch application as a "quality of life" issue. The goal was to be able to apply a series of patches (e.g., 50-100) in approximately 30 seconds. This speed was crucial for quickly identifying and fixing mistakes. The speaker notes that applying patches is less common now due to merging other people's code.

Unacceptable Performance of Other Projects:

The speaker found the performance of other SCM projects unacceptable, citing examples where applying a single patch could take up to 30 seconds.

Scalability Limitations of Existing SCM Systems:

The speaker concludes by stating that existing SCM systems were not designed to be scalable. This limitation further fueled the need for a new approach to source control management.

AI summaries can miss context or contain errors. Check important details against the original video.

MAKE IT YOURS

Read. Remember. Reuse.

Free tools

Go a little deeper.

Have a question about this video? Load its transcript to open the video chat.