On 07/09/2010 07:40 AM, Philip Martin wrote:
> Senthil Kumaran S writes:
>
>> In a repository that contains a large number of files and folders
>> (over 100K), many of which have the needs-lock property set, If any
>> user attempts to check out this entire repository, the large number of
>> locks
Senthil Kumaran S writes:
> In a repository that contains a large number of files and folders
> (over 100K), many of which have the needs-lock property set, If any
> user attempts to check out this entire repository, the large number of
> locks created on the server
> render the server almost unu
Senthil Kumaran S wrote:
Following are my findings,
With svn 1.6.9, in the working copy,
$ time /usr/sbin/svn ls . > /tmp/ls.txt
real0m5.745s
user0m4.281s
sys0m1.653s
$ tail /tmp/ls.txt
test0.txt
test1.txt
test2.txt
test3.txt
test4.txt
test5.txt
test6.t
Hi,
In a repository that contains a large number of files and folders (over 100K),
many of which have the needs-lock property set, If any user attempts to check
out this entire repository, the large number of locks created on the server
render the server almost unusable due to high load and cau
4 matches
Mail list logo