microsoft / microsoft/vscode-cpptools

Settings for using ramdrive for storing temporal IntelliSence data

Open
#13,890 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

docs Language Service performance
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Feature Request

Some data for current project can be placed directly on ramdrive (standard feature in Linux, in Windows more complicated but ImDisk/AIM can make them free). Many developers today have more than 32Gb RAM in notebooks, and >64Gb on desktop.

What need to be implemented

  1. Locating data which can be placed in ramdrives (candidates .browse.VS.db , may be some ipch files)
  2. Some mechanism for controlling livecycle of that data (it can be populated when loading project and deleted from ramdrive when unloading project. This will affect speed of IntelliSence readiness, but extend SSD lifetime ) and ability for disabling it for very large projects (for Chromium source this data won't fit RAM, but many other projects will)

Today cache has no mechanism for removing old data (https://github.com/microsoft/vscode-cpptools/discussions/10637) but ramdrives with deleting cache data after unloading project will help resolve this.

This feature also will increase the lifespan of SSD drives, and may be some other components of will use ramdrive for speedup

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the IntelliSense cache data mentioned in the issue, especially .browse.VS.db and possible ipch files, then trace how project loading and unloading currently manage it. Done would require a configurable ramdrive option, lifecycle cleanup, and a way to disable it for projects whose data is too large.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.