New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance issue due to usage of Powershell #84
Comments
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 |
I believe this is the existing problem for |
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? |
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. |
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). |
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 |
Background Information:
Describe the bug
wslfetch takes a long time to display output (I've seen it vary between 7 and 15 seconds). wslsys takes 1.5-3 seconds itself.
To Reproduce
Steps to reproduce the behavior: Just run wslfetch with no parameters (same for wslsys)
Expected behavior
The output should appear more quickly.
Additional context
I initially suspected that it was Powershell being slow but I can't seem to get it to show in my task manager so I may be wrong. You don't call it THAT many times do you?
I will also investigate on a solution myself.
The text was updated successfully, but these errors were encountered: