Child pages
  • ReSharper Profiling Instructions
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Performance Issues

In order to get a performance snapshot for ReSharper follow these steps:

  1. Download and install dotTrace Performance 4.0 profiler from
  2. Start dotTrace and choose 'Profile'
  3. Select 'Standalone application' in the 'Application kind' list
  4. Point dotTrace to Visual Studio executable (devenv.exe)
  5. Make sure the following options are set:
    1. Progiling type: Tracing
    2. Meter kind: Wall time (performance counter)
    3. Start profiling immediately: on (if you're experiencing performance problems on Visual Studio startup or during solution loading) or off otherwise
  6. Press 'Run'
  7. If there's a performance problem during startup
    1. Wait while Visual Studio starts, open your solution
    2. Wait until the solution is loaded and ReSharper finishes loading caches
    3. Press 'Get Snapshot' button on the 'Control Profiling' window
  8. Otherwise
    1. Wait while Visual Studio starts, open your solution
    2. Press 'Start Profiling' button on the 'Control Profiling' window
    3. Perform actions which are slow with ReSharper (typing, switching between documents, building etc)
    4. Press 'Get Snapshot' button on the 'Control Profiling' window
  9. Save the resulting snapshot

Memory Issues

Prepare environment:

  1. Before starting Visual Studio:
    • Open devenv.exe.config in "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE"
    • In the <runtime> section add <gcConcurrent enabled="false"/>
  2. Download NmpCore.exe
  3. Enable Managed Memory Indicator in ReSharper | Options / Environment / General

Get Snapshot:

  1. Get process ID for devenv.exe process in question
  2. Double-click managed memory indicator in Visual Studio status bar (to the right) to perform Garbage Collection
  3. Execute the following command, substituting <pid> and path to snapshot:


  1. Compress resulting snapshot using Zip
  2. Upload it to
  • No labels