lw @lw@mastodon.bsd.cafe
Public

does anyone use Forgejo and have issues with larger repositories? i a local copy of FreeBSD's ports.git (1.8GB on disk) where a normal 'git pull' from poudriere takes ~10 minutes, which doesn't seem right.

this is on an 8-core server with 2 mirrored SSDs, but the pull seems blocked on a single-threaded, CPU-bound git command: /usr/local/libexec/git-core/git --shallow-file pack-objects --revs --thin --stdout --shallow --delta-base-offset --include-tag

do i need to 'optimise' the repo somehow or what am i missing here? because i don't think this behaviour is normal or expected.

Shawn Webb @lattera@bsd.network
Public

@lw Pre-Forgejo, the project tried for a while to use . But that fell over sideways with src and ports, especially with scraper bots continuously looking up each and every commit.

At the time, the problem stemmed from the fact that the git package that everyone uses will load the entire repo history just to look up a single commit.

Rinse and repeat for thousands of hits per second, and kaboom!

HardenedBSD currently uses a self-hosted Enterprise instance. We're hoping to eventually migrate to .

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://bsd.network/users/lattera/statuses/116171070547084454 on your instance and quote it. (Note that quoting is not supported in Mastodon.)