[solved] RestoreMaxiTree with network drive kills performance
Posted: 24 Mar 2019 19:42
Solution: Use the 32-bit context menu instead of the 64-bit menu. The 64-bit menu is a compiled AutoHotkey script that cannot be fixed because the source code is not available.
(I am not talking about the start up time)
My PC has a NAS permanently attached to it via SAMBA. For a while now I am struggling with an extremely unresponsive XYplorer when I right-click files and folders anywhere (local or network). Often, XYplorer stays unresponsive for >5 seconds.
I narrowed the problem down to RestoreMaxiTree=1 and at least one MaxiTreePaths pointing to my NAS.
When XYplorer starts, I see a CPU and IO spike on my NAS, as expected. Unexpectedly, I see these spikes when I right-click files/folders on my local SSD. This is peculiar, since right-clicking should not affect the state of the tree(s) at all. And even if a file operation would affect a tree on my SSD, the tree(s) on the NAS do not have to be refreshed.
Therefore, I see no reason why XYplorer has to access the network drive so frequently.
Since I love RestoreMaxiTree, I'd appreciate a discussion, and maybe even a fix . As stated above, I do not mind a longer start up time at all.
Edit: I might have to do some more testing with RestoreMaxiTree=0. When the tree shows folders on the network, I might get the same result.
Edit 2: Disabling auto refresh on network drives did not help.
(I am not talking about the start up time)
My PC has a NAS permanently attached to it via SAMBA. For a while now I am struggling with an extremely unresponsive XYplorer when I right-click files and folders anywhere (local or network). Often, XYplorer stays unresponsive for >5 seconds.
I narrowed the problem down to RestoreMaxiTree=1 and at least one MaxiTreePaths pointing to my NAS.
When XYplorer starts, I see a CPU and IO spike on my NAS, as expected. Unexpectedly, I see these spikes when I right-click files/folders on my local SSD. This is peculiar, since right-clicking should not affect the state of the tree(s) at all. And even if a file operation would affect a tree on my SSD, the tree(s) on the NAS do not have to be refreshed.
Therefore, I see no reason why XYplorer has to access the network drive so frequently.
Since I love RestoreMaxiTree, I'd appreciate a discussion, and maybe even a fix . As stated above, I do not mind a longer start up time at all.
Edit: I might have to do some more testing with RestoreMaxiTree=0. When the tree shows folders on the network, I might get the same result.
Edit 2: Disabling auto refresh on network drives did not help.