RustRover 2025.1 Help

Performance tuning tips

This article provides an overview of techniques to help improve RustRover performance when working with large-scale projects.

Increase memory heap

Enable memory indicator

To determine whether performance issues are caused by low heap memory, enable the memory indicator:

  • Navigate to View | Appearance | Status Bar Widgets and select Memory Indicator.

The memory indicator will appear in the bottom-right corner:

Memory indicator

Increase memory heap

  1. Select Help | Change Memory Settings from the main menu.

  2. In the dialog that opens, set a higher memory heap value in the Maximum Heap Size field.

  3. Click Save and Restart.

Increasing heap in the Change Memory Settings dialog

If the amount of free heap memory drops below 5% of the maximum heap size, a warning will appear.

Low memory warning

Click Configure and enter a new heap size value in the dialog that opens.

Speed up code analysis

On-the-fly code analysis is one of the most performance-consuming processes in RustRover. Here's what you can do to lighten it up.

Filter the list of inspections

  • By default, many RustRover inspections are set to run on the fly. To lighten up the process, you can reduce the list of these inspections: navigate to Settings | Editor | Inspections and browse through the list of inspections, clearing the checkboxes for those you prefer not to run on the fly.

    Disable performance-consuming inspections

    You will always be able to run inspections on demand using the Code | Running Code Cleanup with profile ''{0}'' command and explore the results in a separate tool window without affecting the editor. Also, you can postpone code analysis (and on-the-fly refactoring) until commit by setting up the Before Commit options.

Tune analysis for a file

You can configure the highlighting level for the currently opened file: none, syntax, or all problems.

  • Use the inspection widget in the upper-right corner of the editor:

    Inspection widget

Enable Power Save mode

You can enable Power Save Mode or battery efficiency mode using one of the following options:

  • As an alternative to disabling individual checks or files one by one, try using Power Save Mode. This mode disables all inspections and other resource-intensive background tasks across the entire IDE.

    To enable Power Save Mode, go to File | Power Save Mode.

    Power Save Mode enabled
  • Right-click the status bar and select Power Save Mode. The Power Save Mode icon Power Save Mode icon will appear on the status bar.

Speed up indexing

Exclude directories and file types

  • Your project may include folders with binaries, logs, or build artifacts that do not affect RustRover code insight. Indexing such folders can also be resource-intensive due to their size or location. In these cases, it is reasonable to exclude the folders manually: right-click the directory in the project tree and select Mark Directory as | Excluded.

    Mark directory as excluded

    Once files are excluded, their symbols are no longer available to RustRover. The following features will be disabled for excluded files: code completion, auto-import, code generation, Find in Files (except in open files), navigation, and refactoring.

  • You can also exclude files such as logs or generated data by file type. To do so, go to Settings | Editor | File Types and add the pattern to the list of ignored file types:

    Ignored file types

Disable unnecessary plugins

To increase the IDE performance, try disabling the plugins you don't need. You will always be able to turn them on again later.

  1. Go to Settings | Plugins.

  2. Browse the Installed tab and disable the unnecessary plugins:

    Disabling an unnecessary plugin

    You can also disable all manually installed plugins at once (the non-bundled ones) from the menu under The Settings button:

    Disable all downloaded plugins

Report performance problems

If you experience an IDE freeze or high CPU or memory usage, and the tips listed above do not help, please provide us with the IDE logs, thread dumps, and performance snapshots. For details on how to collect and send this information, refer to this instruction.

Last modified: 27 March 2025