Thanks for the response. I did more testing on the 1.12.0 server, and it seems it's only those command options that I think would require querying the server is experiencing the slow down:
e.g. svn status --show-updates directory/file1.txt directory/file2.txt directory/file3.txt <-- this took about 3 seconds and seems to scale according to the number of files as it outputs "Status against revision" for each file. svn status --show-updates directory <-- this took about 1-2 seconds but only output "Status against revision" once. svn info -r HEAD directory/file1.txt directory/file2.txt directory/file3.txt <-- this took about 3 seconds and seems to scale according to the number of files and display info for each file at the rate of 1 file per second svn info -r HEAD -R directory <-- this took about 1-2 seconds even though the entire directory has 17 files and just outputs info for 17 files in one hit The server is on another machine in my local network and both running Windows 10 Pro. Not entirely sure the filesystem you are referring to, but the drive with the repository is running NTFS. On Tue, Jun 4, 2019 at 6:18 PM Johan Corveleyn <jcor...@gmail.com> wrote: > On Tue, Jun 4, 2019 at 7:35 AM Thuan Seah Tan <th...@fmod.com> wrote: > > > > Wondering if anyone has experienced slowness when running commandline > svn if multiple files are passed to svn status or svn info? > > > > For example: > > svn status directory/file1.txt directory/file2.txt directory/file3.txt > > > > In my tests, the output is generated at about the rate of 1 file per > second when doing so. Running svn status on the entire directory > recursively turns out to be much faster. > > Doesn't ring a bell with me. Can you give some more context? > - Which OS? > - Which filesystem? Is it local or a network filesystem? > - Which version of SVN? If not the latest (1.12.0), can you try to > reproduce it with 1.12.0? > > -- > Johan >
