for the last few weeks have been having extremely slow read times on viewing contents of mapped network nas folders. Tried repairing indexing problem in win10 but no change.
I then opened windows file explorer and was astonished it was faster at reading those same files than Opus have ever been. What is the deal here, should I stop using opus or is there a fix I can do?
Opus version Directory Opus Pro 12.28 Build 8189 x64 OS 10.0 (B:19044 P:2 T:1) SP 0.0
Windows 10 Pro 21H2 6/14/2021 19044.1741 Windows Feature Experience Pack 120.2212.4180.0
If it only started happening recently, I would investigate whether there has been an update on the NAS side which may have slowed down (some methods of) directory reading.
That or a config change on the Opus side. (If Opus is configured to read more metadata than before, via columns or label-filters, then that could cause more to be happening involving the NAS while reading its folders.)
The way folder reading works in Opus has not changed in a very long time, so if the problem is only a few weeks old then something else must have changed.
Thanks for the rapid response. I dont think the nas has anything to do with it since windows file explorer is currently lightning faster than anytime I have ever used Opus. There are always package updates for the nas and also there was a good sized windows update a few weeks ago.
I need to understand why the problem is not in windows file explorer but is in Opus? That way i may have a chance of changing some settings in Opus to solve the problem.
Explorer may use a different API to read the directory listing, or Opus may be requesting more data from the drive while or after reading the folder (for different metadata columns, thumbnails, or similar).
(Since it involves the network, it's also possible that firewall/antivirus is treating the two processes differently.)
Thanks for all your insights. Will check out the firewall now. Also, How can I find out which API each program is using? If they are different can I get Opus to use the same one that explorer is using.
Process Monitor is your best bet for seeing what each program is doing when reading the directories.
It might reveal some extra activity that explains the speed difference.
It could also show some API / flags / buffer size differences, although spotting them can be tricky in all the detail.
The stack trace you can get from the Properties dialog for each event can also sometimes reveal if other components are getting involved. Sometimes it'll show antivirus/firewall components, but I think it depends on how they are implemented.
Thanks for all your help and insights. Give me a little time to investigate and I will let you know what I find out.