Optimize for VSCode C++ extension file scan#27245
Merged
Conversation
guschmue
approved these changes
Feb 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Update the settings for VSCode C++ extension to reduce the file scanning. (potentially extend the life of the SSD on the devbox)
Added a few common folders into the exclusion list to help reduce the time of file scanning.
Motivation and Context
By default the VSCode C++ extension will scan all folders in the workspace unless it's excluded. This will cause the default build folder being scanned, which contains 100k+ files and 20k+ C++ source files for a WebGPU build.
A simple analyze of my local workspace: