2

I have been trying to find out why my custom icons were not showing up when accessing the share remotely and found this. As I understand it, the behavior to not load icons on "slow" filesystems is hardcoded.

Why not let the user decide what a "slow" filesystem is? We have an option to not extract previews from remote files by setting the size to 0.
Let the user add filesystems/paths that are to be treated as "slow" in dolphin's settings. Even a config file would be great to have for starters.

I am on a gigabit LAN link, and have several cifs shares mounted via fstab. I'm using the same shares on windows and explorer manages to load the folders and parse the desktop.ini in roughly the same time as dolphin. The impact shouldn't be that high - and even if it is, please let the user decide.

The approach could be to just load the default icon at first, and retrieve the custom icons from .directory in a separate thread one by one, caching the result for the duration of the session. This way, the icons will only have to be re-read if a refresh is triggered, or the window is closed.

The hilarious part about the whole "slow/fast" FSes is that sshfs is declared as "fast" while it's much slower even with a weak cipher for me (60MB/s vs 90MB/s on smb).