Skip to content
Snippets Groups Projects

Performance with git

Closed Performance with git
performance_with_git into master
Closed Marc Radulescu requested to merge performance_with_git into master
Viewing commit 6ba55948
Prev Next
Show latest version
1 file
+ 1
− 3
Compare changes
  • Side-by-side
  • Inline
source/_posts/2014-10-17-performance-benefits-of-switching-to-git.markdown → source/_posts/2014-10-17-geographic-replication-with-git-and-gitlab.markdown
+ 1
− 3
---
layout: post
title: "Performance benefits of switching to git"
title: "Geographic replication with git and GitLab"
date: 2014-10-17 14:08:56 +0200
comments: true
categories:
@@ -17,9 +17,7 @@ This means that even in the case of a server downtime, development can still con
**Server downtime is not as disruptive to the workflow as with a centralized tool.**
After the first cloning of the origin repo, Git only registers the changes to the files, so the deltas between the origin and the clones are very small.
That's less information that needs to travel through the wire.
**Getting the clone in sync with the origin feels instantaneous in most of the cases.**
Code searching is also considerably faster than with a centralized tool, because the search happens on the local clone of the repo.