Turn of solution wide analysis?

[John Woo]

Is there any way I can turn off solution wide analysis and leave it as page wide analysis? The solution wide analysis is always a problem for cpu and memory hog. This is a universal true for other productivity plugins like code rush and resharper. The good thing of resharper is that it allows you to turn the solution wide analysis off and page wide analysis is turn on as default which is sufficient enough for most people.

Another question is how I can turn the short cut "Alt + Enter" on? I Uninstalled my resharper and installed just code. When I tried to this short cut, it did not give me a context menu as I expected. I even tried to restore visual studio short cut key but it did not help.

[Chris]

Hello John,
Yes, having an option to turn off solution wide analysis is on our TODO list. Moreover we'll continue improving the performance and the memory footprint.
Btw can you tell us why would you want to turn the solution wide analysis off? Does it perform slow on your machine or you're worried mostly about the memory footprint?

As for the Alt + Enter shortcut, you could go to JustCode / Options / General and then click the "Restore keyboard shortcuts" button. This should do the job.

Kind regards,

Chris
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[John Woo]

Thanks for your reply. The reason I want to turn off solution wide analysis is because I have a quite big solution (almost 40 projects and tens of thousand lines of code). Every time the analysis kicks in, it really slows down my machine and memory consumption surges. I would happily live with page wide analysis (page wide here means for all opened pages).

As far as short cut "Alt + Enter", I did what you asked, but it still does not help.

[Chris]

Hi John,
To make the Alt + Enter shortcut working you can go to Visual Studio / Tools / Options / Environment / Keyboard and then search for JustCode.FixError. Once you find it you can try to assign the Alt + Enter shortcut to it again. Most probably this shortcut has been taken by some other command you have in your Visual Studio.

Hope this helps.

Regards,
Chris
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Tony]

Seems this thread was started a few years ago regarding turning off solution wide analysis. What I witness still is that the analysis process effectively doubles the amount of memory I use while working in Visual Studio. With my current solution open, VS is using almost 700 MB of memory. The JustCodeAnalysis process is also using almost 700MB of memory.

Is the ability still on your TODO list, or is it supported now and I'm just not seeing the option to turn it off?

[Ivo Bratoev]

Hello,

 We haven't implemented the turning off of the solution wide analysis as we need it for most of our features. We had and still have some ideas for turning off parts of it but we decided that it was better to invest in optimizing the analysis to take as less resources as possible.
Can you give me more info about your solution - how big is it, what kind of projects do you have? Do you use the latest JustCode release? Does the analysis process stay all the time at this memory usage or is it just a peak?
The analysis process peaks during initial analysis of your solution but it should release the resources after that.

Greetings,
Ivo Bratoev
the Telerik team

[Jeremy]

I would also love to be able to turn this off, or at least have it do a better job of figuring out how often it needs to scan things.  We have one solution with 148 separate projects in it, and it scans through the whole thing every time I open it, even if I just closed it.  I don't know whether lowering the process priority would help, as the main slowdown comes from HDD thrashing from Visual Studio and JustCode trying to parse all the source files at the same time.  I don't actually know what your methodology is for things, but I'd do something like this:

1.  When opening the solution, do no analysis until all projects are loaded
2. Once projects are loaded, if there are any open files, analyze those with high priority, including following their references one level down.  If no open files, skip this step.
3. Start a low-priority background scan, beginning with the references of the files from step 2 (assuming there were any), gradually completing the whole solution
4. If at any point a user opens a different file that analysis hasn't yet covered, pause the step 3 scanner, and kick that step 2 scanner into gear for this new file and its references.  Once done, resume the step 3 scanner.

Basically, the idea is to immediately give the user what he needs immediately, and then fill in the gaps in a way that doesn't affect his/her active workflow.

[Mike]

Another thought is caching the Snapshot , if this is not done already  , so that on startup of a project the snapshot is read from disc ,not a full re-parse re analysis of all the source code. The its topped up with files that have been changed.
 
I know Red Gate do that for SQL Prompt , its painful the first time around but very quick after that. I also believe Visual assist X do too for their Intellesense add in.

I appreciate the need for the analysis in providing the basis for the fixes and hints etc , but on 32 Bit Windows (as some mere mortals still run) it does push the limit and leads to OO Memory exceptions. (I abandoned R# for this reason as it regularly crahsed VS . I haven't experienced JC doing this yet).

Strangely MS Dtabase Projects seem to be the worst where you would expect no real analysis going on !

Mike

[Svetlozar]

Hello,

Thank you for your feedback and sorry for the late reply!

When you close a solution JustCode saves the analysis information and on the next opening of the solution it fetches that information again. There shouldn't be analysis refresh if the files haven't been changed.

Please have in mind that the JustCode analysis engine uses an external process so that it doesn't interfere with the Visual Studio process. If you experience slowness in Visual Studio you can try to turn off some of the visual features(like Color identifiers, Structural Highlighting, etc. you can do that from JustCode Options | Visual Features) and the visual hints (JustCode Options | Code Analysis | Hints) .

Regards,
Svetlozar
the Telerik team

[Scott]

There hasn't by chance been a change that allows us to disable the Solution Wide scan, has there?   Unfortunately the project that I've recently been moved to is nearly, if not completely impossible to use Just Code with.   There is approximately 80 projects, and any time a missing class is highlighted, it takes 4+ seconds.  When a change is made that would remove the underlining of a found error (such as a missing reference that Just Code just fixed), it takes another 5+ seconds.

As an avid user and advocate of Just Code, I'm running into a bit of an issue getting buy in from any of the team members on the current project. On previous, and fairly large projects, we haven't seen this level of lag time.  But in this case I've had to remove the toolset for the moment in order to keep productive.

Any thoughts or suggestions would be great!

[Zdravko]

Hello Scott,

 Thank you for your feedback.
We are constantly working on our performance and memory optimizations to make JustCode more stable and faster than before.
The solution wide scan is a base for all other features and especially for the Navigation. That is why it is a vital part of JustCode and there is no option to turn it off.

I have some questions which will help us to investigate this behavior?
1. Could you give us some more details about your projects:
• How many project files are opened in parallel?
• How large are the files you open and does file size make a difference for performance?
• How many warnings/errors JC reports do you have in the whole solution?

2. Would you please archive(ZIP) and send us your JustCode logs from "%localappdata%\JustCode\Logs" folder? This will help us clarify a number of issues.

3. Would you try disabling :
-JustCode's Visual Hints (JustCode Options\Code Analysis\Hints - all checkboxes to be unchecked; 
-JustCode Options\Visual Features, and JustCode Options\Visual Features\Structural Highlighting) 
-Typing Assistance (JustCode Options\Typing Assistance) and see after that whether you will have the same issues with JustCode? Just to make sure that those are not at fault in your environments.

4. How much memory does JustCode use and how much CPU time? 
• Does it happen constantly or it is just a peak?

Thanks.
I look forward to hearing from you.

Regards,
Zdravko
Telerik

[Nathan]

I am new to Telerik.  The first issued that I ran in to was an "Out of Memory" exception when trying to compile / run my solution.  Unfortunately I am using a corporate laptop, Windows 7 (32 bit) maxed at 3.XX Gb.  So, here I am in December of 2013 looking for the same thing that someone was looking for two years ago.  "How do I turn off JustCodeAnalysis".

I understand that it is the base to a lot of things that Telerik does in the background and I understand why you can't just turn it off.  With that I will ask a different question entirely for those of us that are searching for a solution to this issue.

Three questions:
Can you please tell us what you have done to make this issue better over the last 2 to 3 years?  All we seem to get is "NO"

How much memory do you recommend for a system that is going to do development with Telerik?

How can we lessen the pain?

Thanks!!!!!!
Nathan

[Mike]

Hi

I also suffered the dreaded corporate 32 bit PC with limited memory, accountants don't quite understand the PC to match the users requirement argument. We had DELL Inspiron i7 Win 7 32 bit and 4G RAM.



Bottom line was that I had to effectively give up using JC and indeed R# as well as both gobbled more memory that  had. I used Visual Assist X and lived without the additional featured JC & R# have. This add in has a much lower memory requirement but alas a few features short. Coderush is the 4th in the debate and this sort of falls between the 2 extremes but in my opinion is a bit strange to use.



Out of interest I found (empirically) VB and Database projects the worst for OOM errors. It was normally as MS Code Analysis (VS 2010 Ultimate) tripped in on build, again a corporate requirement to duplicate in effect the Code Analysis. In my case the JC & R# were personal licenses and not company provided.



My home PC is an i7 , WIN 8 64 with 8G of memory and I have absolutely no memory issues since I started with it . If that helps.



You can try setting the 3G memory flag that allows more memory to be used , personally I never saw a difference.

.

Mike

[Zdravko]

Hello Nathan,

We make optimizations all the time to improve JustCode productivity.

Here is an article with the recommended requirements, but as bigger the solution is the more memory JustCode consumes.

You can disable all visual features from JustCode Options page > Visual Features except the "Show visual aid setting" and warning providers for the languages you don't use from Options > Code Analysis.
Maybe this will lower your memory consumption.

@All users with the OutOfMemory issue
Take a memory snapshot using JustTrace and send it to use. But this is in case that you can easily reproduce the exception.
Thanks.


Regards,
Zdravko
Telerik