This question is locked. New answers and comments are not allowed.
The memory usage for JustCodeAnalysis is well over 500MB most times.
My solution is large, has 40 sub projects in it. JustCode seems slick and fast when using VS2010 but as time goes on the JustCodeAnalysis.exe overpowers my machine and it grows to a complete crawl.
Is there any way I can tone this down or turn it off? I do not, or at least haven't, used the CodeAnalysis feature yet, so I wondered if I could turn this off.
My solution is large, has 40 sub projects in it. JustCode seems slick and fast when using VS2010 but as time goes on the JustCodeAnalysis.exe overpowers my machine and it grows to a complete crawl.
Is there any way I can tone this down or turn it off? I do not, or at least haven't, used the CodeAnalysis feature yet, so I wondered if I could turn this off.
1 Answer, 1 is accepted
0
Hi!
The JustCodeAnalysis process does all the heavy lifting of JustCode: It checks the whole solution for errors, performs navigation commands and refactorings, etc. In essence everything you do with JustCode requires it. Thus it is not possible to turn it off. So far we have struck the trade-off between memory usage and performance on the side of performance. This is the reason why our whole solution analysis is an order of a magnitude faster than that of our competitors.
Currently we are thinking of making this trade-off configurable, so that it is possible to tell JustCode to be less demanding in its memory use at a cost of being slower in the error analysis, navigation and refactoring commands.
Reported slowdowns are often not caused by the memory the analysis process uses but instead by performance issues in the VS portion of JustCode. In fact if your machine is not memory-starved you should not see any slowdowns by the memory the JustCode analysis process uses. So if you see this slowdown even though you have a lot of physical RAM you might have encountered another problem.
Hans Kratz
the Telerik team
The JustCodeAnalysis process does all the heavy lifting of JustCode: It checks the whole solution for errors, performs navigation commands and refactorings, etc. In essence everything you do with JustCode requires it. Thus it is not possible to turn it off. So far we have struck the trade-off between memory usage and performance on the side of performance. This is the reason why our whole solution analysis is an order of a magnitude faster than that of our competitors.
Currently we are thinking of making this trade-off configurable, so that it is possible to tell JustCode to be less demanding in its memory use at a cost of being slower in the error analysis, navigation and refactoring commands.
Reported slowdowns are often not caused by the memory the analysis process uses but instead by performance issues in the VS portion of JustCode. In fact if your machine is not memory-starved you should not see any slowdowns by the memory the JustCode analysis process uses. So if you see this slowdown even though you have a lot of physical RAM you might have encountered another problem.
Greetings,
Hans Kratz
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>