We are aware that many of our users experience problems with ReSharper performance in Visual Studio. This article contains some troubleshooting suggestions and our plans on improving ReSharper performance. Please look through the list of suggestions and check if any of them helps.
Speeding up Guide
First of all, please refer to the guide specifying which Visual Studio and ReSharper settings can be modified in order to improve performance.
Web languages suggestion
In case you have a web project containing a big amount of JS/TS files and libraries please check if adding these files as third-party code could help.
Investigation of performance issue by ReSharper team
If changing settings doesn’t help we’d be grateful if you could provide us a performance snapshot as described in our article.
We investigate each snapshot and provide a fix if ReSharper is the culprit of the problem.
Still, there are some issues that could be solved only by moving ReSharper out of Visual Studio process.
Out of process
It’s a massive technical refactoring of the core of ReSharper, making everything asynchronous so it can run out of process, but without breaking current Visual Studio integration while it's in development.
We are trying to be transparent and capture our progress in this tracking issue, which additionally collects a lot of background posts about performance.
Visual Studio 2022 support
There’s ReSharper preview version for Visual Studio 2022 published recently, you can find the installer and more details about this version here.
Many of our first users report better performance experience compared to ReSharper integrated into previous Visual Studio versions.
Memory consumption workaround
We also have a workaround that works well for many solutions (and works perfectly for our team) and helps free up memory.
Please note that you are welcome to share any of your concerns by contacting our support team (press "Submit a request" button here) so we can perform a focused investigation of your issue.