[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: enhancement suggestion

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Tue, 20 Feb 2018 15:59:38 +0100

On Tue, Feb 20, 2018 at 1:11 PM, Christian Klie <cklie_at_gmx.de> wrote:
> Hello,
> currently I made a huge commit. In respect of the number of the files (see
> attachment "working copy").
> While the commit went down the transaction grew and grew and grew (see
> attachment "transaction").
> That all happend because of the files in the transaction's folder being very
> small but huge in number so
> those have a relativly huge overheat, because of the blocksize. So I am
> suggesting to rethink the commit procedure but I am not
> sure whether to report this or not.

So the directory 5-6.txn below db/transactions showed:
- Number of files: 244295 (0 folders)
- Size: 88.6 MB
- Size on disk: 29.8 GB
(Wow, that's huge! For only 88.6 MB of data in 244295 files, that's a
factor of more than 300 compared to the actual data size)

And your working copy showed:
- 118094 files, 5350 folders
- Size: 903 MB
- Size on disk: 1.01 GB

What SVN version is the server? What SVN version is the client?
What version of back-end filesystem on the server (BDB or FSFS, which version)?
-> If you have a 1.9 server, please send the output of "svnadmin info
REPOS_PATH". Otherwise, send the contents of REPOS_PATH/format and of
REPOS_PATH/db/format.

The server is on Windows apparently. Which version of Windows? NTFS I
presume? Anything special about that disk? Any special settings?

Oh and one more question: do those files in your working copy have
many svn properties?

-- 
Johan
Received on 2018-02-20 16:00:13 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.