Post a reply

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

aforget

DarkSide wrote:

Any news about this issue?
Directory listing of directories with large amount of files (no symlinks) take ages to load and reloads on almost any activity.


I provided Martin Prikryl with debug logs, and he seemed to determine it was some kind of UI loading issue, and never replied to my e-mails after that. I assume he gave up on it.

I've since switched to FileZilla, and which at least shows the files in a reasonable amount of time (rather than hanging for many minutes or even hours), and has other nice features that WinSCP doesn't.

If anyone finds an SCP client that can more seamlessly handle large numbers of files (or if this is ever fixed in WinSCP), please let us know!
DarkSide

Any news about this issue?
Directory listing of directories with large amount of files (no symlinks) take ages to load and reloads on almost any activity.
aforget

Re: Slow to display contents of very large directories

martin wrote:

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

You will find my address (if you log in) in my forum profile.


Done.
martin

Re: Slow to display contents of very large directories

aforget wrote:

I also have the same problem (ten years later). For directories with many files (hundreds to thousands of text files varying in size from 4KB to several MBs each), it takes a very long time before I can even see the directory's contents, while with PuTTY, a text-based SSH utility, I can see the directory's contents almost instantaneously. I've always had this problem with the Windows-installed version of WinSCP, but it has recently become debilitating because I need to browse the contents of these directories frequently. I'm not sure what more information I could provide, but I hope you can replicate and fix the problem.

Otherwise, I've loved WinSCP for years! I hope I don't need to use another program.

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

You will find my address (if you log in) in my forum profile.
aforget

Re: Slow to display contents of very large directories

Guest wrote:

When displaying the contents of a remote directory containing a very large number of files (8283) the time taken to display is very long (~125 seconds) and local CPU utilisation is very high (~97%).

The time to generate he same directory listing on the remote host is relatively short (shown below):
bash-2.03$ time ls -l > /tmp/zz
real 0m3.673s
user 0m2.500s
sys 0m0.450s

The time taken to transfer the contents of the directory listing (/tmp/zz) to my local machine is about 7 seconds (using compression during the file transfer).

The time taken to change directories, to say the root dir, when the current dir contains a very large number of files is also quite slow (~25 seconds).

None of these problems are Earth shattering but it would be great if they get resolved (optimised) in the future.

In the meantime I'm forced to sensibly implement an archiving plan to ensure I don't have so many files in any given directory.

Thanks for a great product!


I also have the same problem (ten years later). For directories with many files (hundreds to thousands of text files varying in size from 4KB to several MBs each), it takes a very long time before I can even see the directory's contents, while with PuTTY, a text-based SSH utility, I can see the directory's contents almost instantaneously. I've always had this problem with the Windows-installed version of WinSCP, but it has recently become debilitating because I need to browse the contents of these directories frequently. I'm not sure what more information I could provide, but I hope you can replicate and fix the problem.

Otherwise, I've loved WinSCP for years! I hope I don't need to use another program.
rustymonkey

Slowness when opening a directory with large number of files

Hi,

I can describe this issue--it occurs for me using WinSCP (portable) v4.26 running on Windows.

If I browse to a directory containing e.g. 250 files, it takes > 60s for the directory to open--the 'hourglass' icon shows up the entire time and cpu utilization goes to 50%. This occurs whether the directory in question is a local directory or remote directory.

Upon further examination, though, CPU utilization goes up for MsMpEng.exe goes for the duration that the hourglass appears. Apparently, this problem affects other apps as well, and a solution is described at:
https://www.1stbyte.com/2010/02/01/microsoft-security-essentials-msmpeng-exe-using-high-cpu-time/
martin

Re: Same problem

leif wrote:

I'm experiencing the same issue, never happened before, but I recently upgraded to 4.1x and it is rather annoying. Seems to be even worse then the original authors times. Tried upgrading to the newest stable version and the problem is still there.

The topic you follow up is 6 years old, so it is hardly relevant. Can you please describe on your own, how WinSCP behaves for you?
leif

Same problem

I'm experiencing the same issue, never happened before, but I recently upgraded to 4.1x and it is rather annoying. Seems to be even worse then the original authors times. Tried upgrading to the newest stable version and the problem is still there.
Guest

Slow to display contents of very large directories

When displaying the contents of a remote directory containing a very large number of files (8283) the time taken to display is very long (~125 seconds) and local CPU utilisation is very high (~97%).

The time to generate he same directory listing on the remote host is relatively short (shown below):
bash-2.03$ time ls -l > /tmp/zz
real 0m3.673s
user 0m2.500s
sys 0m0.450s

The time taken to transfer the contents of the directory listing (/tmp/zz) to my local machine is about 7 seconds (using compression during the file transfer).

The time taken to change directories, to say the root dir, when the current dir contains a very large number of files is also quite slow (~25 seconds).

None of these problems are Earth shattering but it would be great if they get resolved (optimised) in the future.

In the meantime I'm forced to sensibly implement an archiving plan to ensure I don't have so many files in any given directory.

Thanks for a great product!