Pay attention to the footnote: *8 GB plus 46 GB .git directory
8 GB is still a lot. Would be interesting to know how much of it is actual code and how much is just images and so on.
Exactly, there's no way they wrote 8GB of code.
Facebook's git repo is 54GB
11–20 of 245 posts
Re: Facebook's git repo is 54GB
#12I wonder what their branching strategy is like and how merges are gated with a single codebase of that size?
Re: Facebook's git repo is 54GB
#13Earlier quoted context omitted.
Why's it bad to store source code on Git ?
Its not bad, is really nice, but Git has one problem, when you codebase is big, the process takes a long time, imagine git scanning those 8GB every time you do a commit, that is why Facebook was looking to port all their code to another VCS
Funny you should mention Facebook maybe having performance problems with Git: http://git.661346.n2.nabble.com/Git-performance-results-on-a... (2012)
Re: Facebook's git repo is 54GB
#14I thought I had read an article about facebook switching to perforce due to their really large git repo. Were they at least thinking about it? A quick google comes up with nothing but I could have SWORN I read that.
Not like they dont have the money for it, but that would be a very expensive for them and sort of anti-Open Source, no?
Re: Facebook's git repo is 54GB
#15I bet most of that size is made up from the various dependencies Facebook probably has, though I'm still surprised it's that large. I expected the background worker things, like the facial recognition system for tagging people, and the video re-encoding libs, to be housed on separate repositories. I also wonder if that size includes a snapshot of a subset of Facebook's Graph, so that each developer has a "mini-facebo…
There's gotta be a ton of binaries in there
Re: Facebook's git repo is 54GB
#16Earlier quoted context omitted.
Why's it bad to store source code on Git ?
Its not bad, is really nice, but Git has one problem, when you codebase is big, the process takes a long time, imagine git scanning those 8GB every time you do a commit, that is why Facebook was looking to port all their code to another VCS
This is when a centralized VCS with checkin-checkout concepts really shines. The client only has to check the checked-out files on commit.
Re: Facebook's git repo is 54GB
#17I wonder what their branching strategy is like and how merges are gated with a single codebase of that size?
They aim for a completely linear history. They may even have a policy of not allowing merge commits. It is described in various places on the internet. I like https://secure.phabricator.com/book/phabflavor/article/recom... because it and its sister articles on code review and revision control are terrific reads.
Re: Facebook's git repo is 54GB
#18In terms of engineering tradeoffs, this reminds me of a recent talk by Alan Kay where he says that to build the software of the future, you have to pay extra to get the hardware of the future today. [1] Joel Spolsky called it "throwing money at the problem" when, five years ago he got SSD's for everybody at Fog Creek just to deal with a slow build. [2]
I don't use Facebook, and I'm not suggesting that they're building the software of the future. But surely someone there is smart enough to know that, for this decision, time is on their side.
Re: Facebook's git repo is 54GB
#19I wonder what their branching strategy is like and how merges are gated with a single codebase of that size?
They aim for a completely linear history. They may even have a policy of not allowing merge commits. It is described in various places on the internet. I like https://secure.phabricator.com/book/phabflavor/article/recom... because it and its sister articles on code review and revision control are terrific reads.
Dear everyone: you should be using Phabricator. It is Facebook's collected wisdom about software development expressed in software. It has improved my life substantially. The code review is better than Github's, and their linear, squashed commit philosophy has worked out much better than the way I used to do things.