Visual Studio with ReSharper is slow

We do our best in terms of ReSharper performance, however there are some known and unknown cases where ReSharper can slow down Visual Studio.

Below is a check list that will help you troubleshoot, work around or fix the performance issues with ReSharper.

  1. First of all, make sure that the slowdown is caused by ReSharper, as opposed to a different part of your development environment. To do that, simply suspend ReSharper as described here and check if performance issues are still present. If performance improves noticeably when ReSharper is disabled, proceed to the following steps.
  2. Make sure that ReSharper system requirements are met. Please check your environment against the current system requirements. In addition, using more RAM and a Solid State Drive (SSD) instead of HDD is known to help a lot in improving Visual Studio performance with ReSharper.
  3. Review Visual Studio and ReSharper configuration. For a long list of Visual Studio and ReSharper settings that can be modified in order to improve performance, see Speeding Up ReSharper (and Visual Studio). For a maximum impact with minimum configuration changes, try the following short list:
    • Make sure that ReSharper's Solution-Wide Analysis (SWA) is turned off ("ReSharper | Options | Code Inspection | Settings | Enable solution-wide analysis" should be off).
    • If you're using Git command line or an external Git client, or if you're using a VCS other than Git, or you're working on a solution that's not under version control, please turn off Visual Studio's Git integration ("Tools | Options | Source Control | Current source control plug-in", set to "None", then restart Visual Studio)
    • Review Visual Studio settings listed under "Configuring Visual Studio preferences" in Speeding Up ReSharper (and Visual Studio)
  4. Take a Visual Studio performance snapshot and send it to JetBrains. If completing the steps outlined above didn't help improve performance, please capture a performance snapshot with ReSharper's bundled profiler, and provide it to JetBrains. We will be able to investigate the performance issue and provide specific recommendations for you. To do this, please follow steps described in How to collect a performance snapshot.
164 comments
Comment actions Permalink

Well we all used resharper. The combination of Resharper and Visual studio used to be the best IDE on the marker IMHO. Now. We are in the process of eliminating resharper because it is really really slow in VS 2019. For me it is unusable. Every keyboard hit is lagging the whole IDE. VS keeps suggesting to turn resharper of because it slows down the enviromnent etc. Its a shame to see such a good product to continue this path.

1
Comment actions Permalink

If your solution has 30+ projects, Resharper becomes like something worse than a virus. I causes Visual Studio crashes, slows down your PC.

And none of these suggestions works.

1
Comment actions Permalink

 

Please fix Resharper Performance.

3
Comment actions Permalink

Resharper completely slows my i9 9900K, 64GB of RAM, 2TB NVME SSD system down to a crawl.  Even on small projects!  I am shocked how much of a performance impact this causes.  I have used ReSharper for about 5 years now.  This makes me consider abandoning the software.

3
Comment actions Permalink

Nathaniel - maybe the min system specs are dual Xeon, 1TB RAM and NVME2 IN RAID? How dare we run it on only a single CPU + SSD! :)

We use Dell Precision Workstations with pretty high specs and perfomance is woeful for us.

3
Comment actions Permalink

Courtney - Do we need to get those 56-core Xeons, 4TB of RAM and Intel Optane?  I wonder how well it will perform with that system too.  You would think an 8-core i9 would be more than enough performance to handle this.

2
Comment actions Permalink

Nathaniel - Based on the performance I'm seeing - I'd say that's a definite yes!  50 cores for Resharper and 6 for OS and VS.

1
Comment actions Permalink

Honestly, I think ReSharper would be a great tool to benchmark all new CPUs, although I fear the results might always be the same - the CPU couldn't handle the strain.

1
Comment actions Permalink

Was listening to this podcast the other day https://dotnetcore.show/episode-38-rider-with-kirill-skyrgan/

From that I get the overwhelming impression that they've given up on fixing the performance of resharper and are attempting to move it out of process so that it doesn't suck all of visual studio down with it.  

As much as VS has improved in it's refactoring support over the last couple of years, Resharper is still better.  But for now I have to have it disabled most of the time and only turn it on when I really need it :(

 

0
Comment actions Permalink

Just crashes Visual Studio 2019 constantly while "processing files" or "saving caches", can't use R# at all!!!

0
Comment actions Permalink

Hello Wdcossey,

 

Could you please provide a dump as described in the article? You can do it privately via 'Submit a request' form at the top of the page.

We'd be really grateful for the assistance.
Thank you.

Edited by Angelina Elycheva
0
Comment actions Permalink

I've used resharper with VS most of my professional life as a dev. Whenever VS19 came along, it started getting slower and slower. It got even worse with latest version of VS and .Net Core. After so much rage and the whole computer slowing down, I'm now the point where I have to turn it off if I want to be able to work efficiently.

With or without is day and night. If I turn it on, it becomes so bad that I have to wait for my keystrokes to be printed on screen. I now only activate it when I want to refactor heavily because that's still the best tool out there for such a scenario.

How did a product so good that I was willing to put my own personal money on a license got so bad to the point where I HAVE to turn it off to be able to work??? Even on small .net template projects, come on!

My pessimistic self is saying "because they want you to use Rider instead"... And I'm like no thank you, I'll just remove resharper instead. Or maybe I'll move to VS Code now that resharper isn't holding me back to use VS. 

Shame.

Edited by Yann Lair
3
Comment actions Permalink

The bottom line is having to spend time mucking around with Visual Studio and ReSharper, to attempt to eke out a smidge of performance and make this thing slightly usable, is bullshit. That crap may fly with an ad-supported bit of freeware, but for a paid product, it's unacceptable. Performance has been a known issue to JetBrains for years now, and it is clear that JetBrains is more interested in their other offerings then putting the time into rearchitecting ReSharper to run out of the Visual Studio process. No matter what their articles say, there is no magic combination of settings that will allow large and complicated projects to use ReSharper and work acceptably. Don't get me wrong, I LOVE ReSharper, and because at one point in our history, ReSharper was the best-loved, and most productive tool in our toolbox we have continued to pay them for a product that simply no longer functions. At this point, I can no longer justify paying for this defective product, no matter how good it used to be.

1
Comment actions Permalink

John,

I agree.  I purchased my own copy when Visual Studio 2010 was still the most recent version.  I got the company I used to work for to purchase it for the entire team. I was never this slow.  The fact that a blank Console Application in C# causes Visual Studio 2019 to take between 1-2 minutes to open and become usable is unacceptable.  Disabling ReSharper causes VS 2019 to open in 5 seconds at most.

 

FYI - This is with an i9 processor with 64 GB of RAM and a 2TB NVME SSD.

Edited by Nathaniel
1

Please sign in to leave a comment.

Have more questions?

Submit a request