Bo Berglund wrote on Wed, 03 Jan 2018 07:50 +0100: > Is this a one-time cleanup operation or does it need to be executed > regularly?
Regularly. > I.e. does running "svnadmin pack" on the repo consolidate > the many files into a smaller number of big files and set some > repository property such that it will work that way in the future? The former. > This is what I found in svnbook 1.7 page 178: > > "By concatenating all the files of a completed > shard into a single “pack” file and then removing the original > per-revision files, svnadmin pack reduces the file count within a > given shard down to just a single file." > > and > > "Repacking packed shards is legal, but will have no effect on the disk > usage of the repository." > > What exactly is a "shard"? > Is it one of the numerical directories each containing exactly 1000 > files? > Yes. > If so the "shard" storage on my repos seem to only cost at most 4% > extra disk space compared to using a single file (comparing file sizes > against disk usage). The concern was inode usage, not disk space usage. Packing reduces the number of inodes by 99.8%. > Or will compression of the "svnadmin pack" operation make the combined > size of the files even smaller? I.e. it does not only save unused file > allocation space but actually packs the content even better? 'svnadmin pack' neither recompresses nor redeltifies. It just concatenates the files.
