Hi Andrew,
Thanks for the reply. To clarify my original mail;
I've written a Python script that builds a checkin/label log from our
VSS database using the VSS OLE Automation objects. It then checks the
files out of VSS and in to Subversion using PySvn to access the
Subversion repository. In the script I have the option to set the date
of a subversion checkin to match the time that the VSS checkin occurred.
If I enable this option (which essentially boils down to setting the
svn:date revprop), the checkins take longer and longer. From the debug
prints in the script, it seems to be slowing down whilst trying to check
in to Subversion, not check out from SourceSafe. Also, once the script
has completed access to the repository remains slow even if I restart
the machine hosting the svn data, and my local machine.
I've been messing around with it today and found that if I "svnadmin
recover" and "svnadmin dump" the repository and then "svnadmin load" it
back into a fresh location, everything seems to work at full speed
again. Maybe there is some issue with PySvn and Apache? I'll try using
the script to access a repository over svnserve to see if that makes any
difference.
Cheers,
Jason
-------- Original Message --------
Subject: Re: Performance issues when setting dates from scripts
Date: Mon, 23 May 2005 11:25:49 -0400
From: Andrew Thompson <subversionuser@aktzero.com>
To: Jason Field <jfield@sonaptic.com>
CC: users@subversion.tigris.org
References: <4291F2C4.4090101@sonaptic.com>
Jason Field wrote:
> I've recently been trying to export a VSS repository to Subversion using
> the PySvn bindings.
pysvn looks like a Python library for SVN. Are you saying that you're
using a python script that references pysvn to to export your VSS data?
(huh?)
Or are you're just using pysvn workbench as a user frontend to SVN?
> Everything seems to be working well, except for the
> massive decrease in performance that occurs if I set the script to
> change the date revision property of checkins. Does Subversion require
> that ascending revisions have ascending datestamps?
Are you saying that if you make two repositories, one including the old
dates and one excluding the old dates, the performance of the two
repositories are different? I would consider that very curious...
Wait... Does your "massive decrease in performance" occur during the
post-conversion usage of the SVN repository, or during the export of
data from VSS to SVN. If it's only during the export, I would consider
that a cost of doing business with Microsoft. It *should not* affect
everyday usage.
> I assumed that the
> date property was entirely independant of the revision number but
> perhaps I'm wrong! The performance drop off makes the repository
> unusable unfortunately, and yet it would be very handy to maintain the
> entire VSS structure including dates. Any ideas appreciated!
See recent threads on date ranges over the last few days for the
ramifications. (I can't recall if it was on users@ or dev@.)
--
Andrew Thompson
http://aktzero.com/
Interested in a hosted SVN repository? Email me, let's talk...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
--
----------------------------------------------------
Jason Field
Software Developer
Sonaptic Ltd
tel +44 (0)1494 429368
fax +44 (0)1494 429369
email jfield@sonaptic.com
web www.sonaptic.com
----------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 24 19:14:40 2005