> Fetched naively, that would be over 600 PB of git traffic per day.

This seems like an absurd amount of data / traffic per day. Is there really that much to code that needs changing on a daily basis?

▲

nh2 3 hours ago | parent | next [-]

No, of course not.

As the article explains, "over 600 PB" = 25M code checkouts * 25 GB "compressed working copy".

So "fetched naively" here means doing a full `git clone` on every need for `git checkout`, which of course nobody should do, nor does that refer to "code that needs changing daily".

	▲	steveklabnik 2 hours ago \| parent [-]
		> "fetched naively" here means doing a full `git clone` on every need for `git checkout`, which of course nobody should do, It can be cheaper to do a full clone than a shallow one, because with the shallow one, you can't re-use packfiles. GitHub has fairly regularly asked people to stop doing shallow clones because it's harder on their servers than full ones.

▲

falcor84 2 hours ago | parent | prev | next [-]

I don't think anyone "needs" more than perhaps 640KB of git traffic per day, but we want more.

▲

bjornsing 3 hours ago | parent | prev | next [-]

That 600 PB was mostly agents doing ”git clone” and downloading the entire history of their huge monorepo, as I understand it.

▲

rpunkfu 3 hours ago | parent | prev | next [-]

AI iterate quickly, with 100s of followups to fix results

▲

mmmattt 3 hours ago | parent | prev [-]

No, that’s why they don’t do it that way.