Clangd Indexing Memory Limits for Large C++ Projects

Symbol Database Resource Constraints

CLion utilizes a clangd-based language engine to build a symbol database for real-time code completion and navigation. In projects with extremely large codebases, the background indexing process can lead to significant memory consumption and CPU spikes during the initial scan.

While the IDE supports partial re-indexing to optimize performance after modifications, there is uncertainty regarding the configurable boundaries for the indexing engine's memory footprint. Specifically, it is unclear how to prevent the symbol index from consuming excessive system resources without disabling critical code insight features like 'Find Usages'.

What specific configuration settings exist to bound the memory usage of the clangd process? Is there a mechanism to paginate or limit the scope of the indexed symbol graph for specific project directories?