slow browsing on network drives

[admin]

1) You mean XY gets faster after using another file manager on that network location?

2) Does it get faster only on that particular network location, or on all network locations?

3) If it is slow, what exactly is slow?

[mussor]

1) You mean XY gets faster after using another file manager on that network location?

2) Does it get faster only on that particular network location, or on all network locations?

3) If it is slow, what exactly is slow?

ad 1 & 2 not in my experience
ad 3 for me it just hangs. It becomes unresponsive for mouse input but while it is hanging (loading contents) I can use keyboard to type ahead (or hit page down for example) and once listing of files is done type ahead is applied (or pagedown as well). This type of haning (loading) is not present in WinExplorer or TotalCMD.

[admin]

Describe as exact as you can the last action you are performing before the hang. Preferably along with a screenshot of the complete window while it's hanging.

[mussor]

opening a folder in network location using "Enter" key. Don't know what else to say. See in the video I captured. There is direct comparison how WinExplorer handels that and XY and also fresh instance of XY doing the same job. I'm opening a folder "old" with basicaly some text files. These are on network drive and I'm connected to the network via VPN.

video:
https://youtu.be/hIQ8P2YklAs?si=DiPfuINcmtC7ppOJ

[admin]

"... using "Enter" key. Don't know what else to say." You have no idea what programmers mean when they say "exact". So, what I see from your video is that you paste the whole network path into the address bar, while currently being in the drives listing (aka This PC), and then press ENTER there, right? Then there is something in the status bar like "enumerating servers in ???" ... can't read that. Can you give me the EXACT wording? Also: How many items are in the "Old" (???) folder (the one you double-click later), and what file types are these?

Are you sure these are all ON (they should be):
Cache network servers ON
Assume servers available ON
Use generic icons on network locations ON

I can see that the slowness is crass and totally not normal. The question is WHY?

[admin]

PS: Just for fun try this script with your network path:

Code: Select all

enumshellfolderitems "your network path", "1;2;3;4;5;6";

Is it faster?

[mussor]

thanks for quick reply
as for exact action before - It does not matter if I open the location by browsing to it via mouse clicks, keyboard (folder by folder) or by pasting path to adress bar. The hanging is always the same. This was only the fastest way to show it on video. I using XY on network drives the same way as on local. So I could not find anything else to say about that, sorry )) (also, you wrote "action" not "actions"

using that enumshellfolderitems script - it does list them instantly! no hanging there.
there are 155 items in "old" folder. They are AutoHotKey scripts (.ahk). Basically text files. And some of them are compiled to executables. So 27 exe files, 126 ahk, 1 txt, 1 folder.

Then there is something in the status bar like "enumerating servers in ???"

It says enumerating servers in Síť... (which is Network in czech). Showing only in fresh; instance.

[admin]

Okay, let's do some research! In the next beta version (v26.30.0402) try these three scripts and post the results (right-click the header section and click Copy Subject to Clipboard (see attached image); the listing itself is not needed for the research). It will be interesting what time difference we'll see.

Code: Select all

enumshellfolderitems "your network path", , 0;
enumshellfolderitems "your network path", , 2;
enumshellfolderitems "your network path", , 4;

[mussor]

"(feeling adventurous)"

I run them multiple times:

for 0
155 items contained
Path: \\server\share\data_share\***\AutoHotKey\old
329,312 ms
155 items contained
Path: \\server\share\data_share\***\AutoHotKey\old
197,318 ms
155 items contained
Path: \\server\share\data_share\***\AutoHotKey\old
95,243 ms
155 items contained
Path: \\server\share\data_share\***\AutoHotKey\old
183,623 ms


for 2
155 items contained - Small fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
33,954 ms
155 items contained - Small fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
33,922 ms
155 items contained - Small fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
38,660 ms
155 items contained - Small fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
31,929 ms


for 4
155 items contained - Large fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
43,382 ms
155 items contained - Large fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
1,124 ms
155 items contained - Large fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
32,913 ms
155 items contained - Large fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
1,098 ms
155 items contained - Large fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
29,292 ms
155 items contained - Large fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
29,717 ms
155 items contained - Large fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
1,107 ms
155 items contained - Large fetch
Path: \\server\share\data_share\***\AutoHotKey\old\
36,622 ms


(Those numbers are wierd. The last one - 36,622 ms I would say it took 36sec? But the list showed after a second or so.)
those *** are only to make the post more anonymous)) there are just normal letters there

[admin]

Weird indeed. What is the thousand separator and the decimal separator on your system?

BTW, over here flag 2 is clearly the fastest in all folders I tested (though the difference to flag 4 is small).

BTW, to test the current folder simply use this: enumshellfolderitems <curpath>, , 2;

[mussor]

ah, sorry. I misread those numbers... not 36 sec then -_-
On my system, decimal separator is ","
thousand separator is usually just blank space (" ")

I will test more folders to see if there is some pattern (e.g. file types...)

[mumajs]

1) You mean XY gets faster after using another file manager on that network location?

2) Does it get faster only on that particular network location, or on all network locations?

3) If it is slow, what exactly is slow?

Sorry for the late answer.. I just returned from my vacation

Ad 1)
Nope, I wrote it bad. The correct meaning I wanted to say is that I always thing that something is wrong with the server, network, whatever ( I never thing in first point that something is bad with xyplorer)... and I am trying to troubleshoot what is going on and then I run another file manager and recognize that the issue is really XYPLORER. In others it works smooth. So the next question is I guess connected to my incorrect explenation.

Ad 2)
Xyplorer never get faster. It is still the same. However there are some tricks which can help... It depends how many files are in the location. Big improvement for me is "Use generic icons on network locations ON"... but still... slower then competitors

Ad 3)
Showing the files.Basicaly I wan to have the content of the folder visible and be able to work with them. XYPlorer just shows the rounded circle and I can not do anyting. If generic icons are enabled, then OK, it is faster, but MUCH slower then competitors... I have to say... "than anything else"!

The same as Mussor showed in the video. Xyplorer just shows the folder contect slower then competitors. I know this is not helpful, but use one of them and try to browse NAS or something via VPN and you will see the results

[admin]

Alright. Grab the latest beta and run these tests:

Code: Select all

enumshellfolderitems "your network path", , 0;
enumshellfolderitems "your network path", , 2;
enumshellfolderitems "your network path", , 4;

[jupe]

@mussor: https://www.xyplorer.com/faq-topic.php?id=mse

[mumajs]

Hi Jupe,

that is what I mentioned in previous post. There is not everytime environment you can exclude xyplorer from the antivirus. Sometimes it is managed by somebody else unfortunatelly
I know it could be caused by AV, but why the others works normal and also not excluded?