XYplorer Beta Club

admin wrote: Don't worry about the checking: that's XY's job. Of course, XY checks existence before opening any tab. The point is that there are many ways to check the availability of a server, and the area is not well documented. Hence I make experiments to collect user feedback. You tell me which function works the fastest, I implement it.

uhh, ok:

Path: \\myserverpath
- Check 1: False. Time: 46.611,611 msec
- Check 2: False. Time: 0,045 msec
- Check 3: False. Time: 0,446 msec
- Result...
- Result...
- Check 6: False. Time: 25.709,150 msec (NetShareEnum, Level 1 => 53)
- Check 7: False. Time: 25.841,994 msec (NetShareEnum, Level 0 => 53)
- Check 8: False. Time: 25.817,498 msec (NetShareEnum, Level 2 => 53)
- Check 9: False. Time: 25.520,360 msec (NetShareEnum, Level 502 => 53)
- Check 10: False. Time: 0,086 msec

Check4 and 5 took much longer each (over 1mill msec or so)

ReviewPilot wrote:

admin wrote: Don't worry about the checking: that's XY's job. Of course, XY checks existence before opening any tab. The point is that there are many ways to check the availability of a server, and the area is not well documented. Hence I make experiments to collect user feedback. You tell me which function works the fastest, I implement it.

uhh, ok:

Path: \\myserverpath
- Check 1: False. Time: 46.611,611 msec
- Check 2: False. Time: 0,045 msec
- Check 3: False. Time: 0,446 msec
- Result...
- Result...
- Check 6: False. Time: 25.709,150 msec (NetShareEnum, Level 1 => 53)
- Check 7: False. Time: 25.841,994 msec (NetShareEnum, Level 0 => 53)
- Check 8: False. Time: 25.817,498 msec (NetShareEnum, Level 2 => 53)
- Check 9: False. Time: 25.520,360 msec (NetShareEnum, Level 502 => 53)
- Check 10: False. Time: 0,086 msec

Check4 and 5 took much longer each (over 1mill msec or so)

Thank you. Looks like #2 and #10 are reasonable ways to go...

admin wrote:Thank you. Looks like #2 and #10 are reasonable ways to go...

si.
Also, Check 3 took longer (i.e. 25.783,149 msec) several times..

admin wrote:

ReviewPilot wrote:

admin wrote: Don't worry about the checking: that's XY's job. Of course, XY checks existence before opening any tab. The point is that there are many ways to check the availability of a server, and the area is not well documented. Hence I make experiments to collect user feedback. You tell me which function works the fastest, I implement it.

uhh, ok:

Path: \\myserverpath
- Check 1: False. Time: 46.611,611 msec
- Check 2: False. Time: 0,045 msec
- Check 3: False. Time: 0,446 msec
- Result...
- Result...
- Check 6: False. Time: 25.709,150 msec (NetShareEnum, Level 1 => 53)
- Check 7: False. Time: 25.841,994 msec (NetShareEnum, Level 0 => 53)
- Check 8: False. Time: 25.817,498 msec (NetShareEnum, Level 2 => 53)
- Check 9: False. Time: 25.520,360 msec (NetShareEnum, Level 502 => 53)
- Check 10: False. Time: 0,086 msec

Check4 and 5 took much longer each (over 1mill msec or so)

Thank you. Looks like #2 and #10 are reasonable ways to go...

Ah no, wrong results!
#2 and #10 are not valid tests if you pass a server without a share.

So the best is #3. Could you test whether #3 also works correct if the server exists?

Path: \\workingserver (was hard to find one, hehe)
- Check 1: True. Time: 7,129 msec
- Check 2: False. Time: 0,020 msec
- Check 3: True. Time: 3,520 msec
- Check 4: True. Time: 0,760 msec
- Check 5: True. Time: 0,621 msec
- Check 6: True. Time: 6,096 msec (NetShareEnum, Level 1 => 0)
- Check 7: True. Time: 8,065 msec (NetShareEnum, Level 0 => 0)
- Check 8: False. Time: 2,324 msec (NetShareEnum, Level 2 => 5)
- Check 9: False. Time: 2,271 msec (NetShareEnum, Level 502 => 5)
- Check 10: False. Time: 0,036 msec


The BAD really is Check3 on unavailable server takes quite long often enough

ReviewPilot wrote:Path: \\workingserver (was hard to find one, hehe)
- Check 1: True. Time: 7,129 msec
- Check 2: False. Time: 0,020 msec
- Check 3: True. Time: 3,520 msec
- Check 4: True. Time: 0,760 msec
- Check 5: True. Time: 0,621 msec
- Check 6: True. Time: 6,096 msec (NetShareEnum, Level 1 => 0)
- Check 7: True. Time: 8,065 msec (NetShareEnum, Level 0 => 0)
- Check 8: False. Time: 2,324 msec (NetShareEnum, Level 2 => 5)
- Check 9: False. Time: 2,271 msec (NetShareEnum, Level 502 => 5)
- Check 10: False. Time: 0,036 msec

Good, so #3 is the best for you. XY currently uses #6 and it was determined to be the best quite a while ago and with the help of a couple of users. What to do now? Might well be that the results vary with different network setups, who knows...
So I will give you a tweak...

BTW, note that this test is only applied in XY when "Assume servers are available" = OFF! And you should definitely turn it OFF since your servers cannot be assumed to be available! (Sorry, if I informed you differently before.)

I tested now:
With Share on non-working server:

Path: \\myserver\share\path
- Check 1: False. Time: 93.317,906 msec
- Check 2: False. Time: 25.590,728 msec
- Check 3: False. Time: 25.949,967 msec

- Check 10: False. Time: 0,243 msec (edit: arrghh- now 47.051,659 msec)


Does that help?
Might it be #10? #3 is slow now most time..


edit: hmm thinking twice, I think u mean a local share (E:\) from that server or what? should I test that?

ReviewPilot wrote:I tested now:
With Share on non-working server:

Path: \\myserver\share\path
- Check 1: False. Time: 93.317,906 msec
- Check 2: False. Time: 25.590,728 msec
- Check 3: False. Time: 25.949,967 msec

- Check 10: False. Time: 0,243 msec (edit: arrghh- now 47.051,659 msec)


Does that help?
Might it be #10? #3 is slow now most time..


edit: hmm thinking twice, I think u mean a local share (E:\) from that server or what? should I test that?

No, your test was correct.

It looks like your network is a little unstable...

In the next version try this INI tweak

admin wrote:In the next version try this INI tweak

Code: Select all

[Settings]
CheckServer3=1

Thanks a lot, you are a gem (or so).

ReviewPilot wrote:

admin wrote:In the next version try this INI tweak

Code: Select all

[Settings]
CheckServer3=1

Thanks a lot, you are a gem (or so).

And...?

25 seconds..

hmm. I will keep you informed.