You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Weiss, Holger" <Ho...@continental-corporation.com> on 2019/03/19 16:30:35 UTC

svn up --set-depth exclude takes very long time

Hi,
having a very big working copy (>100GB) want to exclude “folderA” (~2.5GB) from this wc via “svn up –set-depth exclude folderA” .
This command takes very long time – did not finish after 2 days when doing this on a NFS mounted dir.
Even when the wc is on a local disk, it takes very long time (>1day).
I am using SVN 1.7.14.

Why does the “exclude” take such a long time and what can be done to make it faster ?





AW: svn up --set-depth exclude takes very long time

Posted by "Weiss, Holger" <Ho...@continental-corporation.com>.
Hi Pavel,
I will try to update the SVN version, but it is not as easy, as we are using the RHEL7 release and its default repos, due to our company policies.
I guess it is much, much faster to checkout the repository again, than “excluding” and existing folder from the working copy.

Can you briefly elaborate “why” this exclude takes sooo long ?
Does it do special things on each file ?

Thanks
Holger


Von: Pavel Lyalyakin <pa...@visualsvn.com>
Gesendet: Mittwoch, 20. März 2019 18:48
An: Weiss, Holger <Ho...@continental-corporation.com>
Cc: users@subversion.apache.org
Betreff: Re: svn up --set-depth exclude takes very long time

On Wed, Mar 20, 2019 at 8:46 PM Pavel Lyalyakin <pa...@visualsvn.com>> wrote:
Hello Holger,

On Wed, Mar 20, 2019 at 2:33 PM Weiss, Holger <Ho...@continental-corporation.com>> wrote:
>
> Hi,
>
> having a very big working copy (>100GB) want to exclude “folderA” (~2.5GB) from this wc via “svn up –set-depth exclude folderA” .
> This command takes very long time – did not finish after 2 days when doing this on a NFS mounted dir.
> Even when the wc is on a local disk, it takes very long time (>1day).
> I am using SVN 1.7.14.

Note that SVN 1.7.x is not supported and you should plan an upgrade to the latest SVN 1.10.x (LTS) or SVN 1.11.x (regular time-based release) builds.

> Why does the “exclude” take such a long time and what can be done to make it faster ?

I guess that it's not the only operation that is slow on the network share, right? Please, upgrade your SVN client and try the same operation with the exclusive locking option[1]. See SVNBook 1.8 about exclusive-locking runtime configuration option[2].

Here is an example:
[[[
svn update --config-option config:working-copy:exclusive-locking=true –set-depth exclude folderA
]]]

Oops, I forgot the links. Here they are.

[1]: https://subversion.apache.org/docs/release-notes/1.8.html#exclusivelocking
[2]: http://svnbook.red-bean.com/en/1.8/svn.advanced.confarea.html#svn.advanced.confarea.opts.config

--
With best regards,
Pavel Lyalyakin
VisualSVN Team

Re: svn up --set-depth exclude takes very long time

Posted by Pavel Lyalyakin <pa...@visualsvn.com>.
On Wed, Mar 20, 2019 at 8:46 PM Pavel Lyalyakin <
pavel.lyalyakin@visualsvn.com> wrote:

> Hello Holger,
>
> On Wed, Mar 20, 2019 at 2:33 PM Weiss, Holger <
> Holger.Weiss@continental-corporation.com> wrote:
> >
> > Hi,
> >
> > having a very big working copy (>100GB) want to exclude “folderA”
> (~2.5GB) from this wc via “svn up –set-depth exclude folderA” .
> > This command takes very long time – did not finish after 2 days when
> doing this on a NFS mounted dir.
> > Even when the wc is on a local disk, it takes very long time (>1day).
> > I am using SVN 1.7.14.
>
> Note that SVN 1.7.x is not supported and you should plan an upgrade to the
> latest SVN 1.10.x (LTS) or SVN 1.11.x (regular time-based release) builds.
>
> > Why does the “exclude” take such a long time and what can be done to
> make it faster ?
>
> I guess that it's not the only operation that is slow on the network
> share, right? Please, upgrade your SVN client and try the same operation
> with the exclusive locking option[1]. See SVNBook 1.8 about
> exclusive-locking runtime configuration option[2].
>
> Here is an example:
> [[[
> svn update --config-option config:working-copy:exclusive-locking=true
> –set-depth exclude folderA
> ]]]
>

Oops, I forgot the links. Here they are.

[1]:
https://subversion.apache.org/docs/release-notes/1.8.html#exclusivelocking
[2]:
http://svnbook.red-bean.com/en/1.8/svn.advanced.confarea.html#svn.advanced.confarea.opts.config

-- 
With best regards,
Pavel Lyalyakin
VisualSVN Team

Re: svn up --set-depth exclude takes very long time

Posted by Pavel Lyalyakin <pa...@visualsvn.com>.
Hello Holger,

On Wed, Mar 20, 2019 at 2:33 PM Weiss, Holger <
Holger.Weiss@continental-corporation.com> wrote:
>
> Hi,
>
> having a very big working copy (>100GB) want to exclude “folderA”
(~2.5GB) from this wc via “svn up –set-depth exclude folderA” .
> This command takes very long time – did not finish after 2 days when
doing this on a NFS mounted dir.
> Even when the wc is on a local disk, it takes very long time (>1day).
> I am using SVN 1.7.14.

Note that SVN 1.7.x is not supported and you should plan an upgrade to the
latest SVN 1.10.x (LTS) or SVN 1.11.x (regular time-based release) builds.

> Why does the “exclude” take such a long time and what can be done to make
it faster ?

I guess that it's not the only operation that is slow on the network share,
right? Please, upgrade your SVN client and try the same operation with the
exclusive locking option[1]. See SVNBook 1.8 about exclusive-locking
runtime configuration option[2].

Here is an example:
[[[
svn update --config-option config:working-copy:exclusive-locking=true
–set-depth exclude folderA
]]]

--
With best regards,
Pavel Lyalyakin
VisualSVN Team