I downloaded the latest version of just code Q2 2010 and installed it on my machine.
My vs took a very long time to load the project, and after that every thing took a very long time.
I saw on the site that JustCode should work on any size of project, is that really true? My project is over 200,000 lines of code and has almost 8000 classes. I know I should probably do major changes to the project size, since even vs without any add ons is quite slow, but that is not up to me.
Is there a known problem with this size of projects?
Is there anything I can do make things work faster?
Before I installed JustCode I installed Code Rush and had to uninstal that for the same reason.
My machine has 2 gb of ram (I wish I had more), running on xp sp3 vs 2010.
Hope you have a solution for me, I would really like to use JustCode.
Naphtali
28 Answers, 1 is accepted
I am sorry to hear that you experience problems like this with JustCode. Your hardware should be sufficient for this solution provided you have a dual core processor. Memory is likely to be the limiting factor on the system you describe.
There are several ways to improve performance:
- When you open a solution for the first time JustCode takes longer and uses more resources because it analyzes the use DLLs and checks all files in your solution. Once that is done (CPU usage of devenv.exe and JustCodeAnalysis.NET4.exe goes to zero) you can exit, restart Visual Studio and reload the solution. Now JustCode should start faster and will only analyze files you change and those that depend on them.
- Every open file increases CPU and memory usage a bit. So it helps if you try not to keep too many files open.
- Some features take additional resources like "Color identifiers" and "Typing assistance". Both can be disabled in the JustCode Options.
- Memory is probably the most limiting factor. Be careful not to run other memory-hungry applications at the same time or consider installing another 1GB of RAM (if possible).
- You can force JustCode to release some resources by minimizing Visual Studio if you need the memory for something else.
- Disabling background indexing software and virus checkers might help.
- Windows Vista and later have better memory management, in particular for the .NET Large Object Heap. You might want to consider upgrading.
We are continuously reviewing JustCode's resources usage and performance. You can expect further improvements in the version to come.
It would be great if you could also answer a few questions which will give us some idea on where to look for further improvements:
- What kind of solution are you working on. Does it contain a website or web application project?
- What exactly is slow? Here is a list of activities, it would be great if you could copy/paste them to tell us which are slow for you:
- Starting VS (slower than without JC)
- Opening solutions (slower than without JC)
- Open/closing files (slower than without JC)
- Adding/removing files to/from the sln (slower than without JC)
- Scrolling in files (slower than without JC)
- Delay/lag when editing files (slower than without JC)
- Building the sln (slower than without JC)
- Time until JustCode finds errors/removes corrected errors (red underlines)
- Refactoring commands (Rename, etc.)
- Navigation commands (Go to definition, Find usages...)
- Formatting
- Running tests
Hans Kratz
the Telerik team
I am sorry to hear that you are experiencing problems with JustCode.
If you uncheck the checkbox in the "Startup" column of the Add-in Manager dialog for JustCode it will not be loaded when Visual Studio is started. Otherwise each time you start Visual Studio it gets started again. That is the design of the Add-in Manager. I can not reproduce JustCode enabling itself on opening another solution.
"On top of that it creates another instance of Visual Studio 2010 in the task bar which makes things a little confusing. "
This has been fixed and the fix is included in the latest JustCode internal build. The fix will also be included in the upcoming Service Pack.
Regarding memory usage and performance it would be great if you could be more specific. Please have a look at my other response to see what information would help us.
Again please accept our apologies for any problems our software has caused.
Hans Kratz
the Telerik team
The memory footprint of the JustCode analysis process depends on solution size, number of open files and what kind of work is being performed (e.g. it could be more during a global refactoring). In general a memory usage of 250MB can be expected for a medium-sized solution.
In general when striking a tradeoff between memory usage and speed we went a bit more for speed. We will continue to optimize JustCode for speed and performance. Also we plan to make the tradeoff an adjustable option in a future version.
Greetings,
Hans Kratz
the Telerik team
Please stop adding features, the product got Bloated and getting near the point of being useless on a large project.
Again I am really sorry to hear that you have such problems. We are taking this very seriously and will do everything we can to make this work for you. It would be great if you could answer the questions I outlined in the forum post. Also you mention that your project is large. We test JustCode regularly with large solutions and solution size itself is not causing problems. We do have known issues if JustCode reports many warnings/errors or if there are many unit tests. Can you tell me what size your solution is (number of files) and how many warnings/errors are reported by JustCode?
Again thanks a lot for your assistance. If we find a way to fully reproduce the UI responsiveness here in our environment I can assure you that we will fix it ASAP. So any information you can give us is greatly appreciated.
Hans Kratz
the Telerik team
VS without JustCode and any extension cause CPU use for 2-3 of seconds. With JustCode added (and no extension) additional 2-3 seconds - totals 4-6 seconds. Also as soon as I installed VS10x Code map it adds more 2-3 seconds.
I suggest if you try JustCode in environment where multiple most used VS extensions are installed. That should help you find extension that is conflicting and causing slow down.
As Bryan has correctly pointed out each extension affects VS startup time a bit, JustCode is no exception there. Nevertheless the startup time with JustCode is slighlty improved in the Q1 Service Pack release and we will continue to improve it for the Q2 version as well.
Even higher on our priority list is fixing issues where JustCode gets in the way performance-wise while working with Visual Studio (high latency, hangs, feels slow). If you still encounter any such issues with the Service Pack please raise a support ticket so that we can thoroughly investigate the issue.
Regards,
Hans Kratz
the Telerik team
We have found the issue and we are currently working on a fix for the "minimize-restore" problem. Most likely it will be fixed in the next internal build.
All the best,
Ivo Bratoev
the Telerik team
We have published a new internal build with a fix for the problem you have reported. Please give it a try and let us know whether it works for you.
Thanks again and I'm sorry for any inconvenience we might have caused.
Vladi
the Telerik team
- What kind of solution are you working on. Does it contain a website or web application project?
Web Application 150.000+ lines of code, C#, XAML, Entity Framework (Large Model) and WCF
list of activities, it would be great if you could copy/paste them to tell us which are slow for you:
- Starting VS (slower than without JC) --> Without Just Code 2 Secs. With Just Code 50+ seconds
- Opening solutions (slower than without JC) --> about 300% slower
- Open/closing files (slower than without JC) --> Clearly Lagged.
- Adding/removing files to/from the sln (slower than without JC) No chage
- Scrolling in files (slower than without JC) --> No change
- Delay/lag when editing files (slower than without JC) Huuugeeee Lag, can be as 3 seconds betwwen types.
- Building the sln (slower than without JC) is slower
- Time until JustCode finds errors/removes corrected errors (red underlines) Doesn't really matter, is fast enough
- Refactoring commands (Rename, etc.), are fast enough in my opinion
- Navigation commands (Go to definition, Find usages...) are fast enough in my opinion
- Formatting are fast enough in my opinion
- Running tests Not tried them yet.
- i7 with 12 Gigs
Hi, more than 5000+ Warnings. The project has more than 700 files.
Thank you for the follow-up. We'll investigate the problem even further and will improve the performance for the up-coming Q release. We will keep you updated on this one.
Thanks again and if you have more feedback, do send it to us.
Vladi
the Telerik team
the JustCode analysis process itself should not slow down Visual Studio on a multi-core machine with enough available RAM. We are currently investigating some latency issues. If you have any further information which operations become slow under which circumstances and (ideally) how to reproduce this we would greatly appreciate it.
Hans Kratz
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>
I just thought I would comment on here and I am about to uninstall JustCode due to the lag. I really enjoy using it but I've found myself frustrated with 1-3 sec lags even when just hitting the space bar. Visual studio is running in a VM with 5 gigs RAM and quad xeon allocated to it but if I just type or drag the mouse over text, hit the space bar, the CPU can jump up to 25% and everything lags.
My solution has 14 projects but not an enormous amount of classes.
I have noticed though, sometimes the problem does not exist and I'm operating as normal. Most of the time, there is latency though.
-Mike
My 2 penneth
I think Brian (above) comments well, Sluggish behaviour may well be down to other add ins.
When you think what VS itself is doing parsing files for Intellesence , refactoring ,potential compiler errors etc . Now add on Just Code , its sets off to do much the same, and even more for Code Analysis. IS there something else lurking doing it ALL over again ?
I am a self confessed tool addict and I try a lot of add ins , leave em there and you are asking for trouble, trial em and uninstall em
Even the Official MS ones Productivity Power tools etc , may have an impact . (I have no data to prove it but ??) anything that is working around the text editor
As an aside , the code analysis side of JC is the least of my (personal) worries , so I set the files to be checked to only C# and set the refresh frequency to 50000, is once a minute to slow for someone , That way I find in working condition , the sluggishness doesn't show. An initial pass of a project may take time but how often is that ? I assume (?) the result of the first pass is cached somewhere on disc for later use.
My advice is peservere , Telerik are showing themselves (IMHO) as the leader , with good initiatives and a quick response cycle should there need to additions corrections or changes. They frankly showing up their main competitor who is also struggling with memory and performance issues , but are attacking it at what appears to be noticeable lack of gusto.
A Last Aside -- PLEASE can we have intellesense soon , its the only missing feature that makes people look else where.
Mike
Just updated to the latest version. Lasted long enough to do one build of a WPF project. Build time has gone from 4 seconds to 2.5 minutes. Verified that the problem is JustCode by turning it off, 4 second build times return.
The last commercial release does not have the problem but the latest build does.
Why does JustCode get in the way of a build?
Regards
John
Just updated to 2011.3.1221.0 and there is an improvement to build times.
With JustCode running 36 seconds, without 4 seconds. Back to the 2011.3.1116.0 build which means resetting toolbars every time I run VS2010 however that takes less time that the 30 second penalty every time you build a project.
John
we tried to reproduce this issue here but could not so far. For example the Prism v4 Stocktrader RI desktop solution builds in 8 to 10 seconds with and without JustCode on my machine. The JC sln itself also builds in the same time regardless if JC is installed and enabled or not.
So there must be something different in your environment. For the Service Pack we changed the way JustCode watches for filesystem changes so that might be a factor.
It would be great if you could help us tracking down this issue:
Do you have your solution stored on a network share?
Do you use many external files or linked files stored in a separate location?
Is there anything special about your build process, custom build actions, etc.?
Can you reproduce that with every solution on your machine or just with one particular solution?
Hans Kratz
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
Hi Hans,
Sorry for the delay in replying, holidays and all that… Happy New Year…
>>Do you have your solution stored on a network share?
Yes, the entire project is on a network drive
>>Do you use many external files or linked files stored in a separate location?
Yes, lots of linked classes, user controls and references, all to network drives.
>> Is there anything special about your build process, custom build actions, etc.?
Nope, nothing additional
>>Can you reproduce that with every solution on your machine or just with one particular solution?
Happens in most of the network drives based solutions
Regards
John
As a quick follow up, I moved the entire project from the Network to a local drive and the propblem goes away. So it would appear JustCode struggles when the project, links to classes, user controls and/or refrerences are stored on network drives.
Regards
John
John, thanks for reporting this. We will try to reproduce the performance issues you have with solutions residing on a network share here.
Hans Kratz
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
Just wondering if you guys have made any progress on this issue?
Regards
John
unfortunately wee could not reproduce build times being slower with a project residing on a network share. We made some changes to how JustCode checks for file changes which might be responsible though. The next internal build (to be released shortly) will contain refactored code which also does more logging for filesystem updates.
Once released please give it a spin and let us know if it resolves the issue for you.
Regards,
the Telerik team