ReSharper
 
Get ReSharper
Get your hands on the new features ahead of the release by joining the Early Access Program for ReSharper 2025.1! Learn more

Speed up ReSharper (and Visual Studio)

Last modified: 26 May 2024

There are two major sources of performance problems with ReSharper installed in Visual Studio:

  • Your system does not meet the requirements. In this case, we suggest upgrading your system as the first step of dealing with the problems.

    We constantly make sure that ReSharper works fine on modern hardware and with medium- and large-size solutions without any tweaking. We believe that Visual Studio developers are working towards the same things.

    By trying to speed up ReSharper on outdated hardware by disabling some features, you deprive yourself of great tools that can speed up your development performance.

  • Visual Studio and ReSharper, which share the same 32-bit process push your system to its limits. Often, this is reported to happen on large-size solutions and when ReSharper is installed to Visual Studio v. 2015 or later.

    In this case, provided your system meets the requirements, the check-list below will help you fix performance problems in most cases.

A significant time (up to several minutes) taken for opening a large solution for the first time is not a sign of a problem. ReSharper builds and caches a model of the solution, which is then used in almost all of its features — not only for code analysis, but also for navigation and search, code completion, unit testing and more.

Subsequent openings of this solution will not result in any significant delays because the indexing results are already cached on your hard drive.

Note that because ReSharper processes assembly annotations at the very first start, any subsequent start will be faster even if you clean up ReSharper caches.