JetBrains Rider and .NET SDK: Solution-wide Analysis Resource Reclamation

Resource Management in Virtualized Environments

JetBrains Rider employs a dual-process architecture, splitting the frontend IDE from the ReSharper host process. In cloud-based or virtualized development environments, the Solution-wide Analysis (SwA) feature can lead to significant CPU and memory overhead because it continuously scans the entire codebase regardless of which files are currently active.

Memory Behavior Constraints

While Power Save Mode can disable background indexing, there is uncertainty regarding how the ReSharper host process handles memory reclamation when Solution-wide Analysis is toggled off for large-scale .NET solutions. It is unclear if the memory allocated for the global analysis cache is immediately released to the OS or retained for potential reactivation.

Does the ReSharper host process trigger a garbage collection or memory release event immediately upon disabling Solution-wide Analysis? To what extent does the .NET SDK version influence the memory footprint of the analysis cache during this transition?