On Fri, 8 May 2020 at 09:59, clime <clime(a)fedoraproject.org> wrote:
On Thu, 7 May 2020 at 20:58, Kevin Fenzi <kevin(a)scrye.com> wrote:
>
> On Wed, May 06, 2020 at 08:39:19PM +0200, clime wrote:
> ...snip... please folks... please trim your posts? :)
>
> > These are some great stats!
> >
> > But I would like to note that exploded repos (or source-git repos)
> > have at least two other advantages.
> >
> > 1) they consume less space than tarballs for each version because
> > objects in git repo are deduplicated
>
> But they consume tons more inodes which makes them painfull to
> backup/restore/mirror.
But maybe still less painful than to do this with upstream tarballs?
No because the things that backups and rsync do works in a slow way.
We can do the backup the look-aside cache with tar-balls in a couple
of hours. We can also rsync that in the same amount of time. It takes
that long or longer to do that with a couple of git trees which are
much smaller in size but larger in file numbers. Every file in a git
tree is stat'd and while there is some deduplication, there is a lot
of files.
Could this be solved by moving to some other sort of file system
model... possibly but we
a) Have no time to pursue that investigation in a large enough size to
prove/disprove it
b) Have no money to purchase the equipment that these file systems work on.
--
Stephen J Smoogen.