On 2013-08-15, at 14:03, Marco Grubert <grube...@gmail.com> wrote:
> I have heard conflicting statements about the impact of branching in git.
> Let's say we have 100 feature branches that are all stored in a remote repo,
> would that affect performance (CPU/network) in a noticeable way ? How about
> 1000? 100,000 branches? In other words how does git scale with regards to
> number of branches?
Remember that git branches are not copies of the files, they are simply
pointers to commits. So thinking about the two extremes that this allows, you
could have 100,000 pointers (branches) all referring to the same commit. Or you
could have 100k branches each referring to a different commit. Thus a
repository of 100k commits.
Branch lookup and commit checkout times are bound by filesystem and disk
performance. Checkouts might slow down in a repository with a lot of
files/commits. But the branch objects themselves are very lightweight.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.