Performance issue due to usage of Powershell about wslu

[paulstelian97]

I've put in some prints between the lines in wslsys and apparently the lines that run Powershell take a full half-second to run. I will try to devise ways to call cmd.exe instead (and reg query commands) to make it faster. If I succeed, I'll bring up a pull request.

[patrick330602]

I believe this is the existing problem for wslfetch, as it doesn't cache information as neofetch or screenfetch. the performance using powershell.exe and reg.exe is actually pretty similar.

[paulstelian97]

So it means that it's something specific to my system that the performance with powershell.exe is much worse? Considering the same number of calls to a Windows executable (either powershell or reg) from my patch it definitely makes a difference on my system. Does it not on yours?

[patrick330602]

Interesting. I will do another test on virtual machine just for that. I don't want to get into "It works on my machine" situation.

[paulstelian97]

Do try to limit CPU performance (my old laptop had i3-5005u and it took even more than that half-second for Powershell to launch, my current personal laptop has an i5-8250u and still takes that half-second to launch, my work laptop has some i7 [HQ category] and Powershell starts before the window launch animation ends).

[patrick330602]

You are right, on a computer that is not that powerful, the two commands showed a huge speed difference. there's still a little bit things to modify in your PR