lsd is slow Windows

[lzybkr]

Performance is very slow - about 50 seconds to list a few files.

The long delay appears to be in calling lsd::meta::windows_utils::get_acl_access_mask.

Possibly relevant details - I'm testing on Win10 1903 on a domain joined machine. I suspect the issue is contacting the domain controller, because when I disconnect the machine from the network, lsd.exe gives me this error:

cannot access '.': The specified domain either does not exist or could not be contacted. (os error 1355)

I also tested on a non-domain joined machine (Server 2016) and it seemed plenty fast.

[gchamon]

Is windows even supported?

[Peltoche]

Hi!

Is windows even supported?

Yep but it's in early stage for now. I will soon add some documentation into the README.

[gchamon]

Cool, because I was surprised to see Windows issues when I couldn't find anything in the readme. Nice! I will also try it in my secondary windows machine

[Berrysoft]

I tried in Windows and it is as fast as in WSL, sometimes faster. But I do sometimes come across the error cannot access '.' if -a is passed. This error also sometimes happen in WSL when accessing files in Windows.

[pplmx]

very very very slow in win 10, listing a directory with four sub-folders will cost one minute or more.
In WSL, its speed is normal.

[banjo]

Any news on this? The same directory works great in WSL but takes over 20s on Git Bash for me.

[santagada]

I've ran a profiler at it and the problem is all the calls to GetEffectiveRightsForAclW:

[ixzh]

generally 1/10 speed of ls

[zwpaper]

#817 (comment)

This program has a severe performance problem on windows when the number of files to read is large (30+), it blocks almost 100ms untill it starts to render with Core::display, I dug on the issue and its located on the Win32 call to GetEffectiveRightsFromAclW, I don't know why is so expensive.

Proposed solutions:

1. Figure out why that function call is so expensive (maybe we can't solve it)
2. Be more inaccurate on windows about the permissions of the user and group (since its not very relevant on windows systems), for example the libcxx of llvm obtains the permissions of a file assuming its read only and then just checking if the property FILE_ATTRIBUTE_READONLY is set or not, assume that everything is executable and similar "inaccurate stuff"
3. Change the creation of the Meta struct to only retrieve the owner/group permissions if its really needed to display

Hope this helps

@cdecompilador please discuss the performance issue on windows here

[zwpaper]

#484 has some works in progress

[ArnaudKunzi]

I don't know Rust, but is there anything i can do to help #484 go forward? It seems that the (last?) hang up is regarding the PR code coverage?