Author |
Topic |
|
BobClarke
Junior Member
USA
17 Posts |
Posted - Nov 16 2018 : 5:44:08 PM
|
This is for your information, not really a bug report.
I realize Code Inspection is still in beta, and had been using it for awhile, but I had to turn it off because shortly after I begin any code editing, CPU usage by the server jumps to anywhere between 15%-28%, which is too much for me. I don't recall it doing this before, so perhaps the new version of VS2017 is involved.
I am running VS2017 doing C++ coding, Visual Studio version 15.8.9, Windows 10 Pro, Version 1809, OS build 17763.55.
Visual Assist info VA_X.dll file version 10.9.2291.5 built 2018.10.02 DevEnv.exe version 15.8.28010.2050 Professional msenv.dll version 15.0.28010.2050 Comctl32.dll version 6.10.17763.1 Windows 10 10.0 1809 Build 17763.55 8 processors (x86-64, WOW64) Language info: 1252, 0x409
Platform: Project defined Stable Includes: C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v18.4.0\Source; C:\Dev\vcpkg\installed\x64-windows\include; C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v18.5.0\Source; C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\Include\um; C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\winrt; C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\shared; C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\um; C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\UnitTest\include; C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\ucrt; C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\include; C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.15.26726\atlmfc\include; C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.15.26726\include;
Other Includes:
Stable Source Directories: C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v18.4.0\Source; C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v18.5.0\Source; C:\Program Files (x86)\Windows Kits\10\Source\10.0.15063.0\ucrt; C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\src; C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.15.26726\crt\src; C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.15.26726\atlmfc\src\atl; C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.15.26726\atlmfc\src\mfcm; C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.15.26726\atlmfc\src\mfc;
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Nov 17 2018 : 01:19:37 AM
|
You may want to disable to below setting:
VA Options -> Code Inspection (beta) -> Reparse automatically |
|
|
feline
Whole Tomato Software
United Kingdom
19022 Posts |
Posted - Nov 17 2018 : 08:35:26 AM
|
If this does not help you might find it useful to lower the CPU priority for VA's parsing, as explained here:
https://docs.wholetomato.com/default.asp?W774 |
zen is the art of being at one with the two'ness |
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Nov 21 2018 : 12:08:02 AM
|
I've asked about this internally. Starting in build 2283, there was a change made that could have impacted performance in large files. The performance is restored for the next release.
I'm not sure if this is what you were seeing or not. Trying the next build, when it will be released, should answer this question. |
|
|
|
Topic |
|