Rutherther <[email protected]> writes:
Hi Jason,
Jason Conroy <[email protected]> writes:
When I created a fork a few weeks ago, the size of that fork
was
~600 MB. By the time of my next fork on Thursday, that size had
gone up to 1.1 GB, and presently the main repo is at 1.4 GB.
Could you clarify how you figured out it takes that much space?
Are you
checking this on codeberg in your profile in Storage Overview,
or? When
cloning the repo freshly, the .git folder in it is 355M for me.
Rutherther
I see a number (1.1 GB) in the corner of the main page for my fork
[1] which matches the one under "Settings" > "Storage overview" in
my account (it's the only fork I have).
I just tried creating a fresh checkout of this fork, and the
amount of data received over the wire is similar to what you saw,
i.e. much smaller:
Receiving objects: 100% (902504/902504), 321.09 MiB | 11.38
MiB/s, done.
I would doubt it can take up more space on codeberg than
that. And
possibly less if they are using better compression.
You may be more familiar with Forgejo than I am, but this isn't
obvious to me. To make a performant web UI, perhaps some of the
repository data needs to be cached in a separate format which
counts against quota.
BTW, something has changed since my initial message:
https://codeberg.org/guix/guix disk usage is now reported as 512
MB.
Hmmm.
Jason
[1] https://codeberg.org/conroj/guix
