Startup delay when mapped network drive unavailable
Startup delay when mapped network drive unavailable
I've just bought an Nvidia Shield and set it up today so I can access its USB drive on my network. I mapped the Shield's USB drive to L:/ and all is working fine in XY.
But due to something unrelated I was doing earlier, the Shield crashed and the USB drive was no longer visible on the network. When launching XY there was now a big delay before it opened (30 seconds or so). It took me a while to figure out it was due to the Shield being down but I rebooted it and then XY starts up fine instantly.
Did some testing and if I power off the Shield again it makes XY really slow to startup. Windows Explorer has no problem starting when the Shield isn't visible on the network.
A bit of Googling showed some suggestions from the XY forum to help with slow startup/network drives (things like ticking 'No network browsing on startup' and 'use generic icons for super fast browsing' and a few other things) but none of them seemed to help.
Is there anything specific that can help to speed startup if mapped network drives are down?
But due to something unrelated I was doing earlier, the Shield crashed and the USB drive was no longer visible on the network. When launching XY there was now a big delay before it opened (30 seconds or so). It took me a while to figure out it was due to the Shield being down but I rebooted it and then XY starts up fine instantly.
Did some testing and if I power off the Shield again it makes XY really slow to startup. Windows Explorer has no problem starting when the Shield isn't visible on the network.
A bit of Googling showed some suggestions from the XY forum to help with slow startup/network drives (things like ticking 'No network browsing on startup' and 'use generic icons for super fast browsing' and a few other things) but none of them seemed to help.
Is there anything specific that can help to speed startup if mapped network drives are down?
Re: Startup delay when mapped network drive unavailable
Try these:
Configuration | General | Safety Belts, Network | Network | Assume that servers are available
Configuration | General | Safety Belts, Network | Network | Cache network servers
Configuration | General | Safety Belts, Network | Network | Assume that servers are available
Configuration | General | Safety Belts, Network | Network | Cache network servers
Re: Startup delay when mapped network drive unavailable
Thanks, I saw those ones already and had them ticked. Still doesn't help if the drive is down.
Re: Startup delay when mapped network drive unavailable
Make sure this is disabled:
Configuration | General | Startup & Exit | Reconnect mapped network drives on startup
Still an issue?, then run this through the XY address bar and post the results:
Configuration | General | Startup & Exit | Reconnect mapped network drives on startup
Still an issue?, then run this through the XY address bar and post the results:
::text <get loadtimes>
Re: Startup delay when mapped network drive unavailable
Thanks, I already had that setting disabled too though. These are the results for the <get loadtimes>:
With network drive available:
XY ver: XYplorer 22.70.0100
OS: Windows 10 Windows 10, 64-bit, Release 2009, Build 19044.1466
Loaded: 2022-01-21 08:16:44 in 915 ms
Threshold: 10 ms
0 ms: 161 ms - Start Load
161 ms: 11 ms - Init Language
172 ms: 66 ms - Load Language
238 ms: 34 ms - Load Settings
272 ms: 10 ms - Init Custom File Icons
282 ms: 77 ms - Init Controls
359 ms: 153 ms - Init Graphics
512 ms: 15 ms - Init Tabs
527 ms: 33 ms - Create Info Panel
560 ms: 65 ms - Set Interface Font
625 ms: 35 ms - Init Panes
698 ms: 21 ms - Load Mini Tree 3
734 ms: 28 ms - List Change Mode from 0 to 2
763 ms: 22 ms - List Change Mode from 0 to 2
786 ms: 13 ms - Layout Bars
799 ms: 11 ms - Layout Catalog
820 ms: 47 ms - --- Show Window ---
867 ms: 18 ms - Layout Catalog
892 ms: 20 ms - Layout Status Bar
915 ms: - Load Done
MiniTree: Rows=21, Nodes=25, Expanded=5, Mapped Drives=1, Servers=1
Tree Remember State: Yes (19 stored paths)
Pane 1: Items=24/6, Pane 2: Items=1/6, Catalog: Items=34
With network drive powered off:
XY ver: XYplorer 22.70.0100
OS: Windows 10 Windows 10, 64-bit, Release 2009, Build 19044.1466
Loaded: 2022-01-21 08:44:38 in 36,730 ms
Threshold: 10 ms
0 ms: 131 ms - Start Load
140 ms: 62 ms - Load Language
202 ms: 34 ms - Load Settings
244 ms: 23 ms - Init Controls
267 ms: 106 ms - Init Graphics
373 ms: 12 ms - Init Tabs
385 ms: 32 ms - Create Info Panel
417 ms: 60 ms - Set Interface Font
477 ms: 21 ms - Init Panes
533 ms: 13 ms - Load Mini Tree 3
552 ms: 36,039 ms - List Change Mode from 0 to 2
36,591 ms: 19 ms - List Change Mode from 0 to 2
36,619 ms: 11 ms - Layout Catalog
36,639 ms: 38 ms - --- Show Window ---
36,677 ms: 14 ms - Layout Catalog
36,691 ms: 10 ms - Layout List
36,701 ms: 27 ms - Layout Status Bar
36,730 ms: - Load Done
MiniTree: Rows=21, Nodes=25, Expanded=5, Mapped Drives=1, Servers=1
Tree Remember State: Yes (19 stored paths)
Pane 1: Items=28/7, Pane 2: Items=1/7, Catalog: Items=34
I don't know what the values above relate to but in realtime terms it took about 23 seconds to open.
With network drive available:
XY ver: XYplorer 22.70.0100
OS: Windows 10 Windows 10, 64-bit, Release 2009, Build 19044.1466
Loaded: 2022-01-21 08:16:44 in 915 ms
Threshold: 10 ms
0 ms: 161 ms - Start Load
161 ms: 11 ms - Init Language
172 ms: 66 ms - Load Language
238 ms: 34 ms - Load Settings
272 ms: 10 ms - Init Custom File Icons
282 ms: 77 ms - Init Controls
359 ms: 153 ms - Init Graphics
512 ms: 15 ms - Init Tabs
527 ms: 33 ms - Create Info Panel
560 ms: 65 ms - Set Interface Font
625 ms: 35 ms - Init Panes
698 ms: 21 ms - Load Mini Tree 3
734 ms: 28 ms - List Change Mode from 0 to 2
763 ms: 22 ms - List Change Mode from 0 to 2
786 ms: 13 ms - Layout Bars
799 ms: 11 ms - Layout Catalog
820 ms: 47 ms - --- Show Window ---
867 ms: 18 ms - Layout Catalog
892 ms: 20 ms - Layout Status Bar
915 ms: - Load Done
MiniTree: Rows=21, Nodes=25, Expanded=5, Mapped Drives=1, Servers=1
Tree Remember State: Yes (19 stored paths)
Pane 1: Items=24/6, Pane 2: Items=1/6, Catalog: Items=34
With network drive powered off:
XY ver: XYplorer 22.70.0100
OS: Windows 10 Windows 10, 64-bit, Release 2009, Build 19044.1466
Loaded: 2022-01-21 08:44:38 in 36,730 ms
Threshold: 10 ms
0 ms: 131 ms - Start Load
140 ms: 62 ms - Load Language
202 ms: 34 ms - Load Settings
244 ms: 23 ms - Init Controls
267 ms: 106 ms - Init Graphics
373 ms: 12 ms - Init Tabs
385 ms: 32 ms - Create Info Panel
417 ms: 60 ms - Set Interface Font
477 ms: 21 ms - Init Panes
533 ms: 13 ms - Load Mini Tree 3
552 ms: 36,039 ms - List Change Mode from 0 to 2
36,591 ms: 19 ms - List Change Mode from 0 to 2
36,619 ms: 11 ms - Layout Catalog
36,639 ms: 38 ms - --- Show Window ---
36,677 ms: 14 ms - Layout Catalog
36,691 ms: 10 ms - Layout List
36,701 ms: 27 ms - Layout Status Bar
36,730 ms: - Load Done
MiniTree: Rows=21, Nodes=25, Expanded=5, Mapped Drives=1, Servers=1
Tree Remember State: Yes (19 stored paths)
Pane 1: Items=28/7, Pane 2: Items=1/7, Catalog: Items=34
I don't know what the values above relate to but in realtime terms it took about 23 seconds to open.
Re: Startup delay when mapped network drive unavailable
Hmm strange, it looks like you are using MiniTree and have added the mapped drive (& server) to the MiniTree, just as a troubleshooting step can you switch off MiniTree and retry, and make sure to have your startup tab in a normal HDD folder, ie. not on "This PC" page just for now.
Re: Startup delay when mapped network drive unavailable
I turned off the Minitree and made the startup tab default to C:/ and still no difference. This was the loadtimes:
XY ver: XYplorer 22.70.0100
OS: Windows 10 Windows 10, 64-bit, Release 2009, Build 19044.1466
Loaded: 2022-01-21 21:30:41 in 21,668 ms
Threshold: 10 ms
0 ms: 134 ms - Start Load
143 ms: 62 ms - Load Language
205 ms: 33 ms - Load Settings
245 ms: 24 ms - Init Controls
269 ms: 101 ms - Init Graphics
370 ms: 13 ms - Init Tabs
383 ms: 30 ms - Create Info Panel
413 ms: 62 ms - Set Interface Font
475 ms: 21 ms - Init Panes
520 ms: 16 ms - Go Start Path Expanded: C:
549 ms: 21,000 ms - List Change Mode from 0 to 2
21,556 ms: 15 ms - Layout Catalog
21,581 ms: 40 ms - --- Show Window ---
21,621 ms: 12 ms - Layout Catalog
21,633 ms: 10 ms - Layout List
21,643 ms: 23 ms - Layout Status Bar
21,668 ms: - Load Done
MaxiTree: Rows=19, Nodes=25, Expanded=3, Mapped Drives=1
Tree Remember State: Yes (1 stored paths)
Pane 1: Items=10/10, Pane 2: Items=1/6, Catalog: Items=34
I also tried disabling the Catalog but still the same slow start.
XY ver: XYplorer 22.70.0100
OS: Windows 10 Windows 10, 64-bit, Release 2009, Build 19044.1466
Loaded: 2022-01-21 21:30:41 in 21,668 ms
Threshold: 10 ms
0 ms: 134 ms - Start Load
143 ms: 62 ms - Load Language
205 ms: 33 ms - Load Settings
245 ms: 24 ms - Init Controls
269 ms: 101 ms - Init Graphics
370 ms: 13 ms - Init Tabs
383 ms: 30 ms - Create Info Panel
413 ms: 62 ms - Set Interface Font
475 ms: 21 ms - Init Panes
520 ms: 16 ms - Go Start Path Expanded: C:
549 ms: 21,000 ms - List Change Mode from 0 to 2
21,556 ms: 15 ms - Layout Catalog
21,581 ms: 40 ms - --- Show Window ---
21,621 ms: 12 ms - Layout Catalog
21,633 ms: 10 ms - Layout List
21,643 ms: 23 ms - Layout Status Bar
21,668 ms: - Load Done
MaxiTree: Rows=19, Nodes=25, Expanded=3, Mapped Drives=1
Tree Remember State: Yes (1 stored paths)
Pane 1: Items=10/10, Pane 2: Items=1/6, Catalog: Items=34
I also tried disabling the Catalog but still the same slow start.
Re: Startup delay when mapped network drive unavailable
Well I am out of ideas, I always have unavailable mapped drives and suffer no startup delays, maybe the dev will have some suggestions for you when he reads this.
Re: Startup delay when mapped network drive unavailable
Thanks for your suggestions, I'll keep tinkering. The problem seems to be related to 'List Change Mode from 0 to 2' so I guess I should start there.
Re: Startup delay when mapped network drive unavailable
Yeah correct, only the dev will know all whats involved behind the scenes in that step.
-
- Site Admin
- Posts: 60598
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Startup delay when mapped network drive unavailable
I have a suspicion. The next beta has a new load log event "List Change Mode UpdateIcons IN" right after "List Change Mode from...".
FAQ | XY News RSS | XY Twitter
Re: Startup delay when mapped network drive unavailable
This was the log after today's update (seemed even slower to start with the network drive down):
XY ver: XYplorer 22.70.0200
OS: Windows 10 Windows 10, 64-bit, Release 2009, Build 19044.1466
Loaded: 2022-01-26 10:14:40 in 74,898 ms
Threshold: 10 ms
0 ms: 182 ms - Start Load
182 ms: 11 ms - Init Language
193 ms: 80 ms - Load Language
273 ms: 41 ms - Load Settings
323 ms: 28 ms - Init Controls
351 ms: 124 ms - Init Graphics
475 ms: 16 ms - Init Tabs
491 ms: 43 ms - Create Info Panel
534 ms: 73 ms - Set Interface Font
607 ms: 25 ms - Init Panes
663 ms: 15 ms - Load Mini Tree 3
686 ms: 73,892 ms - List Change Mode UpdateIcons OUT
74,578 ms: 21 ms - List Change Mode UpdateIcons OUT
74,600 ms: 14 ms - Layout Bars
74,614 ms: 14 ms - Layout Catalog
74,628 ms: 12 ms - Layout List
74,644 ms: 90 ms - --- Show Window ---
74,734 ms: 20 ms - Layout Catalog
74,754 ms: 11 ms - Layout List
74,765 ms: 129 ms - Layout Status Bar
74,898 ms: - Load Done
MiniTree: Rows=11, Nodes=17, Expanded=3, Mapped Drives=1, Servers=1
Tree Remember State: Yes (11 stored paths)
Pane 1: Items=24/6, Pane 2: Items=1/6, Catalog: Items=34
XY ver: XYplorer 22.70.0200
OS: Windows 10 Windows 10, 64-bit, Release 2009, Build 19044.1466
Loaded: 2022-01-26 10:14:40 in 74,898 ms
Threshold: 10 ms
0 ms: 182 ms - Start Load
182 ms: 11 ms - Init Language
193 ms: 80 ms - Load Language
273 ms: 41 ms - Load Settings
323 ms: 28 ms - Init Controls
351 ms: 124 ms - Init Graphics
475 ms: 16 ms - Init Tabs
491 ms: 43 ms - Create Info Panel
534 ms: 73 ms - Set Interface Font
607 ms: 25 ms - Init Panes
663 ms: 15 ms - Load Mini Tree 3
686 ms: 73,892 ms - List Change Mode UpdateIcons OUT
74,578 ms: 21 ms - List Change Mode UpdateIcons OUT
74,600 ms: 14 ms - Layout Bars
74,614 ms: 14 ms - Layout Catalog
74,628 ms: 12 ms - Layout List
74,644 ms: 90 ms - --- Show Window ---
74,734 ms: 20 ms - Layout Catalog
74,754 ms: 11 ms - Layout List
74,765 ms: 129 ms - Layout Status Bar
74,898 ms: - Load Done
MiniTree: Rows=11, Nodes=17, Expanded=3, Mapped Drives=1, Servers=1
Tree Remember State: Yes (11 stored paths)
Pane 1: Items=24/6, Pane 2: Items=1/6, Catalog: Items=34
-
- Site Admin
- Posts: 60598
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Startup delay when mapped network drive unavailable
Hmm, my suspicion was wrong. I will add some new log entries to the next beta. We will find the culprit...
Are you sure that "No network browsing on startup" is ticked?
Are you sure that "No network browsing on startup" is ticked?
FAQ | XY News RSS | XY Twitter
Re: Startup delay when mapped network drive unavailable
Thanks, I appreciate your help and yes 'No network browsing...' is definitely ticked.
-
- Site Admin
- Posts: 60598
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Startup delay when mapped network drive unavailable
1) Is this ticked? Configuration | General | Safety Belts, Network | Network | Cache network servers
2) Are you starting on a mapped drive? (= is the startup path on a mapped drive?)
3) Is your tree locked?
4) In the next beta use this new command to show the load log:
2) Are you starting on a mapped drive? (= is the startup path on a mapped drive?)
3) Is your tree locked?
4) In the next beta use this new command to show the load log:
llog 0;
It will show the complete log without any threshold.FAQ | XY News RSS | XY Twitter