Unraid: Network folder takes 15 seconds to open vs 0.5 on Windows Explorer

Hi folks,

I hope I will be able to find a fix for this, I recently moved my stuff to Unraid and my main machine is plugged directly to the server without the overhead of the router.

They both use 2.5gbit ethernet adapters so bottlenecks should not be an issue here.

When opening a big folder that I have containing 5000++ videos with Dopus, it takes exactly 15 seconds to open that network location vs 0 seconds on Windows Explorer.

This happens in all types of views (thumbnails, details, etc.).

If it can help pin point the issue, I do use tooltips, I do load network folders normally instead of the lazy loading default and I do use that new 'file tree' view that appeared in Dopus 13 if I recall correctly.

I do not calculate folder sizes though, I kept that with the 'on-demand' ctrl+k default.

I also tried by having a connection that goes through the router and the results as expected were a tiny bit slower for both because of the overhead but Explorer still takes less than a second.

The same happens for most file operations like copies and such.

I remember a time where I left Windows Explorer specifically because of it being slow but now when it comes to anything network or FTP related it seems that Directory Opus lost it's edge in terms of performance...

I hope this will be addressed at some point as more and more home consumers have NAS systems or rent servers.

Thanks in advance if anyone has a fix for this.

When using Details mode, which columns are turned on?

If Preferences / Filtering and Sorting / Sorting / Sort shortcuts to folders like folders is on, try turning it off.

If the server's SMB settings have an option named something like Enable wildcard search cache (the name of it in Synology DSM, but it may vary on other setups), turn that on. It takes a while to have an effect, but will give a massive performance increase to directory read speed. (Not needed with actual Windows servers, but greatly speeds up Linux servers that are pretending to be Windows.)

How fast can you list the directory from a command prompt? Or any other tools?

It takes less than a second to a ls command from powershell so cmd should be even faster, also I do not have access to such an option in Unraid it seems:

This seems like a very common problem with UnRAID, affecting a lot more than just Opus.

Some threads I found suggest installing a plugin called Dynamix Cache Directories, although some people found other solutions worked instead.

(Not a complete list. There a lots of other threads about UnRAID directory-listing performance problems on the web. I don't know why it's faster in some tools than others either, but it doesn't seem unique to Opus at all.)

If it's a common problem with Unraid only, how come Windows Explorer loads the exact same directory without any issue within the same time frame as it would load any directory?

I tried other file explorers and they load it in less than a second as well. This includes your 14.95$ competitor.

If they all did that then I could agree with the theory but here in this case only Dopus is affected.

The answer to "how come Windows Explorer..." is because Explorer is the only thing that most manufacturers test against.

It doesn't take 15 seconds to open a folder in Opus on, for example, a Synology server. Opus does exactly the same thing there as it would be doing for Unraid, so how come only Unraid has the problem with Opus?

Given that there apparently lots of reports about Unraid being slow, and they are not all in relation to Opus, why do you assume it's something Opus is doing wrong?

Yes but in this case all the other file explorers load it without issues, if it was a case where the issue could be reproduced elsewhere I would agree with that as it would make more sense.

But in this case they all load the directory quickly (Dolphin, XYplorer, double commander, one commander) on the same OS.

This happens even if I disable all columns and show the files in details mode without thumbnails.

I am quite sure I could reproduce this performance issue by creating a non-Unraid network location from another machine and trying to access it in the same way.

Sounds like a good experiment to try.

I will let you know the results when I get to it.

Ok so after experimenting for a while I took some time to find the issue but what improved it for me was:

-Enabling case-sensitive names on the share

-Disabling macOS interoperability in Unraid settings

-Disable support for extended attributes and handle it in dopus config

-Disable storage of DOS attributes

-Disable support for hardlinks

You were right and I apologize, turning these off in Unraid made it behave just like all the others.

It seems that all the options put together brings an improvement but others who have this issue can try to play around with this.

I think disabling hard links and extended attributes is what helps the most.