UI latency during concurrent builds with solution-wide analysis enabled

Rider runs solution-wide analysis in a separate backend process while the UI remains responsive. On large solutions, concurrent operations such as building, NuGet restore, or opening many files can compete with that backend process for CPU and memory, producing latency that appears only under concurrent requests. The analysis scope and severity rules are configurable, and the feature can be disabled or limited to opened files, but it is unclear whether Rider automatically pauses or deprioritizes solution-wide analysis during a build.

Assume a recent Rider major version where solution-wide analysis defaults are version-sensitive. The goal is to confirm whether this contention is expected behavior or a configurable threshold, and whether disabling analysis for unopened files changes the outcome.

Does Rider throttle solution-wide analysis during concurrent build or restore operations? Is the backend resource contention documented as expected for large solutions? Which setting controls analysis priority relative to solution operations?