Closed Salil03 closed 2 years ago
This is very helpful, didn't know about this analysis before. As you say #76 hopefully fix the problem, but probably the issue is with most of the work done synchronously.
I think everything done synchronously is the problem. We should go async(parallelization) wherever possible
I'll keep this issue open while async mechanism is not in place.
@Salil03 I expect that #80 should solve big part of the problem, if that is the case after version 0.3.0 is published let me know
CPU-20200517T034222.873Z.cpuprofile.txt Here is the profile after the bundling
Here are activation times:
"activationTimes": {
"codeLoadingTime": 106,
"activateCallTime": 13409,
"activateResolvedTime": 37,
}
@mfornet The actual reason for this was #132 . The checker was being compiled every time I ran the testcases. Which created an illusion of high CPU load.
Well, this shouldn't be a problem anymore, given we are compiling only if there are changes. closing the issue.
Only if #132 works on all os. I think only windows has sol.exe
, all others are sol
right?
Only if #132 works on all os. I think only windows has
sol.exe
, all others aresol
right?
Yes, this is correct. Only windows uses .exe
Performance
acmx
0.2.9
Windows_NT x64 10.0.18363
1.45.1
marx24.acmx-unresponsive.cpuprofile.txt
Here are the activation times:
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load
76 might solve it.