--- title: Rethinking C++ Performance: Faster Code Navigation and... description: Visual Studio Insiders 18.9 introduces Whole Codebase Indexing (WCI) for C++, a new deep indexing approach that stores richer symbol information in the browse... canonical: https://daily.dev/posts/rethinking-c-performance-faster-code-navigation-and-github-copilot-tools-with-whole-codebase-inde-hjpdiofdz twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Rethinking C++ Performance: Faster Code Navigation and GitHub Copilot Tools with Whole Codebase Indexing | daily.dev og:description: Visual Studio Insiders 18.9 introduces Whole Codebase Indexing (WCI) for C++, a new deep indexing approach that stores richer symbol information in the browse... og:url: https://daily.dev/posts/rethinking-c-performance-faster-code-navigation-and-github-copilot-tools-with-whole-codebase-inde-hjpdiofdz og:image: https://api.daily.dev/og/posts/hjPDIofDz.png og:image:alt: Rethinking C++ Performance: Faster Code Navigation and GitHub Copilot Tools with Whole Codebase Indexing og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Rethinking C++ Performance: Faster Code Navigation and GitHub Copilot Tools with Whole Codebase Indexing **[DevBlogs](https://daily.dev/sources/devblogs)** · 8 min read · 7 upvotes · 1 comments ## Summary Visual Studio Insiders 18.9 introduces Whole Codebase Indexing (WCI) for C++, a new deep indexing approach that stores richer symbol information in the browse database. WCI delivers 2x or greater performance improvements for semantic file colorization and Find All References operations, with some operations becoming nearly instantaneous. It also powers a new CodeLens references feature for C++ (highly requested), and accelerates GitHub Copilot's find_symbol tool by giving it faster access to symbol context. Technically, WCI expands the browse database to track symbol usages using the full IntelliSense engine, acting as a caching layer that progressively indexes files on demand. The feature is in preview in Visual Studio 2026 v18.9 and requires a minimum of 4 CPU cores. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is whole codebase indexing (WCI) in Visual Studio for C++ projects? Whole codebase indexing is a preview feature in Visual Studio Insiders 18.9 that expands the existing C++ browse database to track symbol usages in addition to declarations and definitions, using the full IntelliSense engine rather than the faster but less precise TagParser. It delivers 2x or greater speed improvements for code navigation and semantic colorization in many codebases, and is enabled via Tools > Options > Languages > C/C++ > IntelliSense. _Developers evaluating faster C++ tooling can track feature rollouts like whole codebase indexing on daily.dev._ ### What are the hardware requirements for enabling whole codebase indexing in Visual Studio 2026? Machines need a minimum of 4 cores to use whole codebase indexing, matching the recommended minimum hardware requirement for Visual Studio 2026. Building the symbol index also consumes additional processing and memory resources compared to the prior approach, and progress can be checked via a task notification labeled 'Running deep C++ analysis for richer navigation'. _Teams planning a Visual Studio 2026 upgrade can weigh hardware needs like these using daily.dev._ ### How does whole codebase indexing improve GitHub Copilot's agentic suggestions for C++ code? Whole codebase indexing gives Copilot's find_symbol tool faster access to symbol-level context by expanding the symbol index that backs language service protocol operations. This lets Copilot locate types, functions, declarations, and definitions across a codebase more quickly, reducing time spent searching for symbol information and making the agentic loop more responsive, especially in larger codebases with many reference locations. _Developers wiring Copilot into large C++ codebases can follow tooling changes like this on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@jenueldev** · 0 upvotes > The progressive, on-demand indexing is the interesting tradeoff here: it avoids making project-open time the full price of richer semantics while still amortizing repeated navigation work. I’d be curious to see peak memory and index-size comparisons for WCI on LLVM, since those costs will determine how broadly teams enable “parse all files.” --- Tags: [#devtools](https://daily.dev/tags/devtools), [#github](https://daily.dev/tags/github), [#c++](https://daily.dev/tags/c++), [#visual-studio](https://daily.dev/tags/visual-studio) [View this post on daily.dev](https://daily.dev/posts/rethinking-c-performance-faster-code-navigation-and-github-copilot-tools-with-whole-codebase-inde-hjpdiofdz) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Rethinking C++ Performance: Faster Code Navigation and GitHub Copilot Tools with Whole Codebase Indexing","url":"https://daily.dev/posts/rethinking-c-performance-faster-code-navigation-and-github-copilot-tools-with-whole-codebase-inde-hjpdiofdz","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/rethinking-c-performance-faster-code-navigation-and-github-copilot-tools-with-whole-codebase-inde-hjpdiofdz"},"datePublished":"2026-07-14T22:29:11.401Z","dateModified":"2026-09-13T20:16:45.587Z","description":"Visual Studio Insiders 18.9 introduces Whole Codebase Indexing (WCI) for C++, a new deep indexing approach that stores richer symbol information in the browse...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e8a14ba5aaadb9e8a6a8fa5f2f0f44e1?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e8a14ba5aaadb9e8a6a8fa5f2f0f44e1?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"DevBlogs","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"DevBlogs","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/8f68b453325f482ebeb73fb780092713","url":"https://daily.dev/sources/devblogs"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/rethinking-c-performance-faster-code-navigation-and-github-copilot-tools-with-whole-codebase-inde-hjpdiofdz","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":7},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"devtools,github,c++,visual-studio","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DevBlogs","item":"https://daily.dev/sources/devblogs"},{"@type":"ListItem","position":3,"name":"Rethinking C++ Performance: Faster Code Navigation and GitHub Copilot Tools with Whole Codebase Indexing"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/rethinking-c-performance-faster-code-navigation-and-github-copilot-tools-with-whole-codebase-inde-hjpdiofdz","comment":[{"@type":"Comment","text":"The progressive, on-demand indexing is the interesting tradeoff here: it avoids making project-open time the full price of richer semantics while still amortizing repeated navigation work. I’d be curious to see peak memory and index-size comparisons for WCI on LLVM, since those costs will determine how broadly teams enable “parse all files.”","datePublished":"2026-07-17T02:14:18.835Z","url":"https://daily.dev/posts/hjPDIofDz#c-IgmCiUTm1","author":{"@type":"Person","name":"Jenuel Oras Ganawed","url":"https://daily.dev/jenueldev","image":"https://media.daily.dev/image/upload/s--BadmiNyj--/f_auto/v1787625077/avatars/avatar_JJtZr4Sjm?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/rethinking-c-performance-faster-code-navigation-and-github-copilot-tools-with-whole-codebase-inde-hjpdiofdz#faq","mainEntity":[{"@type":"Question","name":"What is whole codebase indexing (WCI) in Visual Studio for C++ projects?","acceptedAnswer":{"@type":"Answer","text":"Whole codebase indexing is a preview feature in Visual Studio Insiders 18.9 that expands the existing C++ browse database to track symbol usages in addition to declarations and definitions, using the full IntelliSense engine rather than the faster but less precise TagParser. It delivers 2x or greater speed improvements for code navigation and semantic colorization in many codebases, and is enabled via Tools > Options > Languages > C/C++ > IntelliSense. Developers evaluating faster C++ tooling can track feature rollouts like whole codebase indexing on daily.dev."}},{"@type":"Question","name":"What are the hardware requirements for enabling whole codebase indexing in Visual Studio 2026?","acceptedAnswer":{"@type":"Answer","text":"Machines need a minimum of 4 cores to use whole codebase indexing, matching the recommended minimum hardware requirement for Visual Studio 2026. Building the symbol index also consumes additional processing and memory resources compared to the prior approach, and progress can be checked via a task notification labeled 'Running deep C++ analysis for richer navigation'. Teams planning a Visual Studio 2026 upgrade can weigh hardware needs like these using daily.dev."}},{"@type":"Question","name":"How does whole codebase indexing improve GitHub Copilot's agentic suggestions for C++ code?","acceptedAnswer":{"@type":"Answer","text":"Whole codebase indexing gives Copilot's find_symbol tool faster access to symbol-level context by expanding the symbol index that backs language service protocol operations. This lets Copilot locate types, functions, declarations, and definitions across a codebase more quickly, reducing time spent searching for symbol information and making the agentic loop more responsive, especially in larger codebases with many reference locations. Developers wiring Copilot into large C++ codebases can follow tooling changes like this on daily.dev."}}]} ```