VS Code Performance Setup for Low-End Machines (My Real Workflow)

After writing about optimising my old Ryzen 7 3700U laptop, I wanted to go deeper into one specific tool: VS Code. It’s my main editor, but on older hardware it can feel slow, especially during startup or when switching between large files. Over time, I’ve built a setup that keeps VS Code responsive even on a low-end machine.

This is the exact configuration I use on my Gateway GWNR71539 running Windows 11 Home.

My Machine

• Gateway GWNR71539
  


• Ryzen 7 3700U
  


• 16 GB RAM
  


• Vega 10 graphics
  


• Windows 11 Home
  


• Daily tools: Python, GitHub Desktop, WSL, VS Code

The Problems I Had

Before tuning anything, VS Code had a few issues:

• Slow startup
  


• Extensions taking too long to activate
  


• High RAM usage with multiple windows
  


• Stutters when switching files
  


• CPU spikes when using the integrated terminal
  

Most of this wasn’t VS Code’s fault — it was my hardware. But with the right setup, it became much smoother.

1. Removing Unnecessary Extensions

Extensions are the biggest cause of slow startup. I removed anything I didn’t use regularly and kept only:

• Python
  


• GitLens
  


• Prettier
  


• WSL
  


• A theme
  


• A file icon pack
  

Everything else was slowing things down.

2. Disabling Extension Auto-Activation

Some extensions activate even when you don’t need them. I disabled auto-activation for anything non-essential.

Add this to settings.json:

{

  "extensions.autoCheckUpdates": false,

  "extensions.autoUpdate": false,

  "extensions.ignoreRecommendations": true

}

3. Turning Off Telemetry and Crash Reporting

Telemetry isn’t heavy, but on older CPUs every background task matters.

{

  "telemetry.telemetryLevel": "off",

  "telemetry.enableCrashReporter": false

}

4. Enabling Performance Mode

VS Code has a performance mode that disables some animations and features that slow things down.

{

  "workbench.experimental.usePerformanceMode": true

}

5. Switching to a Lightweight Theme

Heavy themes slow down rendering. I switched to a minimal theme with no fancy effects. It made scrolling smoother and reduced CPU usage during typing.

6. Disabling Workspace Trust

Workspace Trust adds security, but it also adds overhead. On a personal machine, I don’t need it.

{

  "security.workspace.trust.enabled": false

}

7. Optimising the Integrated Terminal

The terminal renderer was causing CPU spikes. I switched to a simpler renderer:

{

  "terminal.integrated.gpuAcceleration": "off",

  "terminal.integrated.rendererType": "dom"

}

8. Reducing File Watcher Load

VS Code watches files for changes, but on Windows this can be heavy. I excluded folders I never touch.

{

  "files.watcherExclude": {

    "**/node_modules": true,

    "**/.git": true,

    "**/dist": true,

    "**/build": true

  }

}

9. Using a Single-Window Workflow

Opening multiple VS Code windows on a low-end machine is a guaranteed way to hit 100% RAM. I switched to a single-window workflow and use tabs instead.

This alone made a big difference.

10. Keeping Projects Clean

Large projects slow down indexing. I now:

• Delete old virtual environments
  


• Clear out unused folders
  


• Remove old logs
  


• Keep dependencies minimal
  

A clean project loads faster and uses less RAM.

Results

After applying all these changes:

• VS Code opens in a few seconds
  


• Extensions activate faster
  


• Terminal is smoother
  


• CPU spikes are less frequent
  


• RAM usage is more stable
  


• Switching files feels instant
  

It’s still an older laptop, but VS Code now feels genuinely usable and responsive.

Final Thoughts

You don’t need a high-end machine to write code. VS Code can run well on older hardware if you tune it properly. These changes helped me get more life out of my Ryzen 7 3700U laptop, and hopefully they help someone else in the same situation.