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

Re: svn commit: r1079008 - /subversion/trunk/subversion/svnadmin/main.c

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 08 Mar 2011 13:46:23 +0000

stefan2_at_apache.org writes:

> Author: stefan2
> Date: Mon Mar 7 22:57:04 2011
> New Revision: 1079008
> URL: http://svn.apache.org/viewvc?rev=1079008&view=rev
> Log:
> Set FSFS cache default size to 16 MB. This is the same default as
> for everybody else, namely the server processes. Thus, it should
> be reasonable value on the same machines.

16MB may be "reasonable" for normal usage but it still has a significant
effect on the testsuite. The testsuite is an unusual access pattern, it
runs thousands of commands on small repositories. Using a 1MB cache I
can run the testsuite for ra_local/FSFS in 10m15s, with 16MB cache that
increases to 12m30s, a 20% increase. There is a similar increase when
testing ra_svn/FSFS using the default Linux svnserve (a threaded
svnserve has a shared cache so isn't affected).

svnserve and svnadmin both have a -M option, was there any discussion
about using a single letter option for this feature? This could be used
by the testuite to restrict the cache size, but for ra_local/FSFS
testing there is no way to restrict the svn client.

Should we add the -M option to the svn client?

Should we make it configurable via .subversion/config instead or as well?

If svnadmin gets configured by .subversion/config should we remove the
command line option?

Received on 2011-03-08 14:53:44 CET

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

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