On Fri, Dec 2, 2011 at 8:19 AM, i_maliavko <i_maliavko_at_wargaming.net> wrote:
> I'm using it since official release. And decision to using it was my big
> fail. Becase:
> 1. commit list makes about 10 minutes time after time;
> 2. first update in day last over 15 minutes;
Hard to say whether this is a regression, without having a comparison
with your old version. How long did 1.6 take in these scenarios?
And: which OS and filesystem?
> I'm working on big project (over 100 000 files) and waste about an hour on
> waiting SVN operations. And the saddest thing that this operations takes my
> HDD off and now I have no time to back to the old SVN version. All my
> programms and IDEs are very busy within updating process. I hope you'll fix
> yours problems with new version but I'll also try to solve it on my working
> place by ubdating OS and all drivers.
1.7 seems to be slower for some operations when the working copy is on
a network drive (NFS, CIFS, ...). Is this the case? If so, can you try
and compare it to a similar working copy on a local drive?
Also: maybe try running 'svn cleanup' on the entire working copy. (SVN
keeps track in its metadata of last-modified times of the files. If
both the last-modified time and filesize are still the same, SVN
assumes the file is unchanged. Otherwise, it will always read+checksum
the entire file to determine if it is still unchanged, which is quite
a bit slower. Sometimes the metadata of the timestamps isn't correct
anymore, for instance because the working-copy was copied (without
preserving last-modified times), or because something 'touched' it.
Obviously this can give a serious performance hit. 'svn cleanup',
among other things, restores the correct timestamps in the metadata.)
Received on 2011-12-04 21:17:09 CET