I'm experiencing a very severe performance issue with VS2015. We have recently moved to VS2015 from VS2013 for our project. I am finding that very often (not 100% consistent) I am getting 50-90% CPU usage on idle when our ASP.NET MVC project is open.
Here's a typical CPU usage scenario:
VS2013
App launch with opening of our project - CPU usage ~50-90%
After around 10-15 seconds - CPU usage ~0-5% and stays there
App close - CPU usage decreases and goes to 0 as app is closed
VS2015
App launch with opening of our project - CPU usage ~50-90%
After around 10-15 seconds - CPU usage ~50-90% and stays there
App close - CPU usage stays at ~50-90% mark and often just hands there. Closing the app is sometimes unsuccessful, with VS2015 giving an "Error Encountered" on close, forcing us to use Task Manager to kill the process.
We are using Pro for both 2013 and 2015. Extensions used are StyleCop, ReSharper 9.2 and Productivity Power Tools (for Column guides only). The extensions are the same for both 2013 and 2015. We have tried uninstalling/disabling the extensions with no performance improvement. The issue is present for a couple of our developers, but not all...
System Config
* MacBook Pro with Windows 10 running in Bootcamp
Fixes attempted
Disable Git source control provider - no performance change
Disable ReSharper/StyleCop - slight performance improvement, but idle CPU usage issue remains
Update VS2015 to Update 1 - no performance improvement
Upgrade from Windows 8.1 to Windows 10 (unrelated to the actual performance issue) - no performance improvement
Re-install of VS2015 - no performance improvement
Disable antivirus (in case it somehow was getting upset with the configuration) - no performance improvement
Unload some of the solution projects - inconsistent performance improvement. It looks like when the non-UI projects are loaded, the performance issue is not present. Once we load 1 of the 2 UI projects, the issue has a 50/50 chance of occurring. Once both projects are loaded, the issue has about 90% chance of occurring. So this is pointing to the UI projects being the culprits, but there is nothing special about those projects - a bunch of controllers and views with some UI util classes along with .css and .js libraries. This change in performance is only present in VS2015 - VS2013 is perfectly happy with all projects. Another point going against the UI projects being to blame is that another WinForms solution which is small in size is having the exact same performance issue in VS2015, while a larger ASP.NET solution is perfectly fine :(
We are trying to move to C# 6.0 and as VS2013 is not supporting that, this is causing us quite a bit of grief..
Any thoughts or advice? Thanks!
Related
I am trying to set up an ASP.NET (.NET framework v4.7.2) Web API. When I debug and try to access the values doc page (/Help/Api/GET-api-Values), it takes between 1.7 min and 2 min to load (time according to the network tab).
I have tried it with and without updating the NuGet packages. I have tried FF and Chrome. I have tried it on my SATA and my SSD. I have re-created the project several times. I cannot get this to go any faster and I have not made any changes or addition to the project at all, all I do is create the project and hit debug. I have checked my resources and I am hovering around 40% CPU and 33% memory so it's not a resource issue. I should also mention that going from the home page to the api list page (/Help) works fine.
Any help would be appreciated
Clean install (or moving to pro) was the solution.
I updated my VS and a SR developer helped me look at the issue during a mentoring session, we could not get it to work so after 40min he suggested a clean install and said to try my pro license while I was at it. I suspect it was the clean install rather then moving to pro but I can't say 100% it was one or the other though. Unless pro lets vs use multiple cores because on community edition it was using 1 core and maxing that core out so my cpu looked ok at a glance but a deeper dive showed issues.
Our company decided to virtualize everything into EC2 and that includes our development machines. The machines are instance type T3 large and we are using Visual Studio 2019 16.9 as of this morning. The performance seems to be horrible for all of our developers. Every time we build, node takes over the CPU and then stays high. Intellisense is laggy.
We do not have any extensions running, just the stock VS2019 install. The solutions is pretty small. It consists of 3 C# projects; DTOs, Controllers, and a Web Site.
I wonder if this has something to do with EBS being relatively slow.
Has anyone had better success?
I'm getting into ASP.NET, and I'm using MVC 5 to build my applications while I follow some Pluralsight trainings. I noticed that in the video training the instructor's Visual Studio builds really fast, but in my computer, after I modify something, every time I build it usually takes from 90 to 120 seconds for the build to finish and I be able to navigate through my application on the browser.
My laptop isn't super old or slow, since it has a Core i5 with 4GB of RAM and an SSD. I've tried to set the MvcBuildViews attribute to false, but still the problem persists. I'm using Visual Studio 2015 Enterprise with Update 2.
Any ideas on what should be the problem?
Delete everything under
C:\Users\YOUR_USER_NAME\AppData\Local\Microsoft\WebSiteCache
Check here too
C:\Users\YOUR_USER_NAME\AppData\Local\Temp\Temporary ASP.NET Files\siteName
It seems like it was a problem with Visual Studio 2015 Update 2. Once I installed Updated 3 it got way faster to build. I noticed that now the IIS Express isn't closed between builds, so now when I build my MVC projects I usually see the result on the browser in less than 20 seconds.
This is not much of an answer that will solve this problem for you. But, I specifically run into this issue with ASP.NET applications. With one of our solutions we have nearly 60 projects and that takes WAY to long to fully build and debug inside a browser from VS.
How I solved this was to point one of our servers with IIS to the folder that my presentation project builds too. This way when the web project is built I can browse my IIS website and see the changes. The downside to this is I can't actively debug in VS easily.
As far as speeding up VS to build this faster with debugging I have had no luck with my experience. From messing with symbol loads, just my code settings, VS IIS settings, but nothing has truly fixed this for me.
I have Windows 7/64 Pro box with Visual Studio 2012 Ultimate, revised to Update 4, with a problem.
Over the last week, I've started experiencing a problem that was originally tolerable, but now has grown worse to a matter of unusability, and I'm in need of some (any?) suggestions. It may turn out this is more appropriate over as a Microsoft issue moreso than a purely programming issue, but I thought perhaps someone might have experienced the issue, hence I'm taking a shot here.
The problem: The VS2012 IDE, moments after starting, seizes with no solution or project loaded, going into "Not Responding" mode, never to return. Worse, however, is that when this occurs, it blocks the OS from starting any 32-bit processes, and 64-bit processes aren't exactly responsive.
This had occurred only once or twice in the last week, and thus I assumed it was an odd/one-off situation and didn't think it was a chronic problem. Today became chronic. Whereas over the last few days this symptom was unusual, today it prevented me from working in VS2012 all day. The VS2012 IDE would be responsive for a brief time, then seize up.
Doing a bit of research on the nature of the issue, and observing it didn't occur until I started VS2012, I began to realize it must be associated with the native VS executable or the ancillary devenv.exe that starts along with it. The real culprit, however, was the Microsoft.VisualStudio.Web.Host.exe executable that provides the web version of the VS hosting environment that was causing the problem.
When the VS2012 IDE would seize, killing the Web.Host.exe process would immediately free the IDE for a time, and allow any "queued" 32-bit apps to start. However, the symptom would return as soon as the web hosting process restarted.
I have updated VS2012 to Update 4, and performed a repair installation of VS2012, and nothing has changed. There are no errors in the event logs that would indicate hardware issues (such as a hard drive failure) or any other lower-level/organic OS issues. There's really nothing to configure (that I know of) on the web host process side, so short of a complete reinstall of VS2012, I'm not sure what else to try.
I saw a fleeting resemblance to this error in a Microsoft Connect forum, but the symptoms were not, in fact, identical, and the prescribed fix (VS2012 up to Update 4) was to no avail.
Edit: Minor bit of additional information - the only unusual element that might prove an "x-factor" in this situation is the recent switch to TFS - within the last week - frighteningly coincident with the onset of the problem. But thinking the SCC provider would be less interested in the content than supporting things like Intellisense, debugging, and the like, I had a tough time convincing myself it would be a player. At this point, however, who knows.
Any suggestions appreciated.
Regret that I can only offer a general solution for this - after updating to Update 4, I then performed a Repair Install of Visual Studio 2012, and since that time, this lockup problem has not recurred. I can't say if a particular library was updated or reinstalled, or if some configuration setting was changed, but either way (so far) VS 2012 is happy and I'm working again. Will update with more information if I find it.
I've encountered a problem where part way through building a solution, VS 2010 becomes locked and never returns. If I build individual projects one by one it works so the building of project is working. The solution contains XNA projects for various platforms and winforms libraries. This did work up until a point but have found no explanation for the sudden freezing.
I've uninstalled all of my plugins to see if that helps but no difference.
In task manager, VS2010 is busy doing something as it's using CPU and consuming memory >1GB.
It took a significant amount of time/removed music to sort it.