News for hackers. Stuff that matters.
Re:Improving large monorepo performance on GitHub by andrewstuart2 on Tuesday March 16, 2021 @07:03PM (#26484363)
> I'm not sure what other answer you're expecting?

I've seen some things. Binaries, large files, isos, generally just any large file with no lines that somebody just didn't know better and committed, changed a few bytes a few times, and generated huge deltas quickly.

I'm far more surprised you don't know what he was expecting than I am that he asked, considering how many times I've run into this in the past.

Re:Improving large monorepo performance on GitHub by chrisseaton on Tuesday March 16, 2021 @07:08PM (#26484404)
If people want a concrete example, here's a 6 GB repo that's 90% Java, 5% C, then some other languages.

https://github.com/oracle/graal

It's not even a mono-repo - this is just part of the project.

Maybe someone's got some tools that let them dig around in the history and find large things or explain why it's so large? I don't think they've been checking ISOs in.

Re:Improving large monorepo performance on GitHub by cmurphycode on Tuesday March 16, 2021 @10:05PM (#26485672)
I was really taken aback by this given my previous experience with the Linux kernel git repo size. So, I just checked out Graal.

Receiving objects: 100% (981372/981372), 187.08 MiB | 6.39 MiB/s, done.

% du -sh graal 328M graal

% du -sh .git 221M .git

And that includes many binary files that were added and removed over time, but not filter-branched out of existence, including jars, pngs, pdfs :)

(https://stackoverflow.com/questions/10622179/how-to-find-ide...)

Re:Improving large monorepo performance on GitHub by chrisseaton on Tuesday March 16, 2021 @10:10PM (#26485694)
Huh... maybe I have a degenerate copy for having it so long and I should try running the compression commands myself.
Re:Improving large monorepo performance on GitHub by lathiat on Tuesday March 16, 2021 @11:28PM (#26486177)
See also “git prune” to remove references to branches and objects no longer on the remote server. Check the docs though I think in some cases I might delete local branches or objects so make a backup first.
Re:Improving large monorepo performance on GitHub by andrewstuart2 on Tuesday March 16, 2021 @08:29PM (#26485070)
I'm totally not surprised that large repos exist, without having fallen prey to any antipatterns. Just saying that I know "have you committed any binaries, dependencies, generated code, etc" are the first questions I tend to ask when somebody tells me their repo is massive. In part selection bias, though, because usually the people working on super old projects know exactly why.
Re:Improving large monorepo performance on GitHub by neolog on Tuesday March 16, 2021 @08:57PM (#26485274)
Re:Improving large monorepo performance on GitHub by cerved on Wednesday March 17, 2021 @03:21AM (#26487585)
git filter repo has tools for analyzing history
Re:Improving large monorepo performance on GitHub by masklinn on Wednesday March 17, 2021 @05:27AM (#26488512)
Nope, the answer is exactly what’s above, this is a large and old project with a fair amount of churn. There are assets in there but they’re a small minority of the issue.

The biggest issue is actually the l10n stuff. It’s all text with lines but there is a lot of it and historically the exports were not really ordered so every major update to the translation files scrambled everything.