I've had to put some repos on my personal git forge instance behind authentication because the LLM companies were consuming multiple CPU cores and causing the memory usage to balloon to unreasonable levels. They were loading every file for every commit in the repo, one by one. Its not as big of a problem for my personal repos, but I mirror some large repos so my CI isn't putting unreasonable strain on the upstream projects. Once I put in the auth wall, my CPU usage dropped to basically nothing, my containers stopped getting OOM killed, and my CI jobs started finishing in shorter amounts of time.
Comments
I've had to put some repos on my personal git forge instance behind authentication because the LLM companies were consuming multiple CPU cores and causing the memory usage to balloon to unreasonable levels. They were loading every file for every commit in the repo, one by one. Its not as big of a problem for my personal repos, but I mirror some large repos so my CI isn't putting unreasonable strain on the upstream projects. Once I put in the auth wall, my CPU usage dropped to basically nothing, my containers stopped getting OOM killed, and my CI jobs started finishing in shorter amounts of time.