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

RE: Significant checkout performance degradation between 1.6.1 and 1.7b2

From: Ketting, Michael <michael.ketting_at_rubicon.eu>
Date: Thu, 11 Aug 2011 08:53:31 +0000

Just a bit more information:
I've now also tried the chekcout tests with other other big trunks in our company:
One took 7min (svn 1.6) vs 9min (svn 1.7), the other 4min (svn 1.6) vs 6min (svn 1.7), so, both are slower but in the range also measured with the benchmarks.
Looks like my own project really is the worst case scenario :)

Regards, Michael
________________________________
From: Mark Phippard [markphip_at_gmail.com]
Sent: Tuesday, August 09, 2011 17:05
To: Ketting, Michael
Cc: dev_at_subversion.apache.org
Subject: Re: Significant checkout performance degradation between 1.6.1 and 1.7b2

On Tue, Aug 9, 2011 at 8:07 AM, Mark Phippard <markphip_at_gmail.com<mailto:markphip_at_gmail.com>> wrote:
Is this via http? Given that export is slower I'd be willing to bet the performance difference is from the new http client library - serf. It is typically slower than Neon. Try switching to neon and run it again.

I updated to the latest Beta of TortoiseSVN and it looks to me like they have changed the default HTTP client to Neon already. So unless you have specifically made serf the default client in your servers file it is not likely that this is your problem.

I developed a set of open-source benchmarks to measure Subversion performance that you can get here:

https://ctf.open.collab.net/sf/sfmain/do/viewProject/projects.csvn

Perhaps you could set up the repository on your server and run the benchmarks using 1.6 and 1.7 to see what kind of results you see? When I run the tests I see considerable performance gain with 1.7. The "FolderTests" are probably the closes tests to your scenario. It will be easier to focus on any remaining performance issues if we can identify and measure them in an open and consistent manner so we can see progress and the impact of different changes.

If these benchmarks do not show the same problems you see on your real code, then we need to add more benchmarks so that we can capture whatever the problem is.

--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2011-08-11 10:54:27 CEST

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