iirc remember some years ago the homebrew repo caused too much load due to their architecture where every client would pull on install or update. Or something l

iirc remember some years ago the homebrew repo caused too much load due to their architecture where every client would pull on install or update. Or something like that. Part of the GitHub response afaik included the info that they went as far as they could with dedicated and beefier servers but asked for a software fix. I would think that if GitHub anticipates a normal repo growing this large they can give it the special treatment