Disabled at 22 million commits
programming.dev
Disabled at 22 million commits
1–10 of 145 posts
Re: Disabled at 22 million commits
#2Re: Disabled at 22 million commits
#3[flagged]
Re: Disabled at 22 million commits
#4[flagged]
What? That's not how Git works, even ignoring packfiles.
(And yes I have no idea what Github's backend does, but I can't imagine "duplicate all data for every commit" would be a feasible implementation strategy.)
Re: Disabled at 22 million commits
#5[flagged]
While it's correct that each Git commit is a snapshot of the worktree, and not a diff, Git uses copy-on-write / structural sharing, which means that generally speaking adding a commit to your repository is a very cheap operation storage wise.
Recommended reading if you're interested in Git's data model, it's pretty easy to understand compared to Git's UI: https://git-scm.com/book/en/v2/Git-Internals-Git-Objects
Re: Disabled at 22 million commits
#6[flagged]
hopefully this is a sarcastic comment. T_T
Re: Disabled at 22 million commits
#7> I decided to see how many commits GitHub (and git) could take before acting kind of wonky. At ~19 million commits (and counting) to master: it’s wonky.
This just doesn't seem right to me. Why? Its obvious at some point you'll harm the service. If the goal was to test it, why not try locally with git.
Re: Disabled at 22 million commits
#8This feels slightly malicious, but I can’t help but admire the curiosity that takes someone to actually see what happens if. That said, now we know, so nobody else needs to bother GitHub engineers by doing this again, hopefully.
Re: Disabled at 22 million commits
#9So the author was purposefully trying to do the most extreme thing they could to see how git/GitHub act/break.
I don’t blame GH at all.
Source: https://web.archive.org/web/20230702215522/https://sh.itjust...
Re: Disabled at 22 million commits
#10[flagged]
as pointed out in the sibling comments, that's not right, but also it can't possibly be right: torvalds/linux has about 1.2M commits, and according to https://cdn.kernel.org/pub/linux/kernel/v6.x/, the current Linux kernel source size is 131M after compression, so (assuming the kernel size has grown linearly with each commit) each maintainer would need to have 75 TB of storage on their personal machine?