Prompt
My IDE feels too slow for modern coding work, what should I fix?
Latest observation
Oct 16, 2026
OpenAI APIWeb search: off
If your IDE feels slow, the biggest gains usually come from fixing a few common bottlenecks rather than “more CPU” in the abstract. Here’s the practical order I’d check:
1) Indexing and file watching
- Exclude big folders from the IDE:
node_modules,dist,build,.venv,target,out, logs, generated code, large data dirs. - Reduce the size of the workspace if possible.
- If you have huge monorepos, open the relevant subfolder instead of the repo root.
2) Extensions/plugins
- Disable anything you don’t actively use.
- Watch especially for:
- linters
- formatters
- Git integrations
- AI assistants
- language servers for languages you aren’t editing
- Re-enable one by one to find the slow one.
3) Language server / analysis settings
- Heavy features can slow responsiveness:
- deep type checking
- real-time linting on every keystroke
- auto-import scanning across the whole repo
- expensive code inspections
- Consider lowering the aggressiveness or running some checks on save instead of continuously.
4) Disk speed
- IDEs depend heavily on fast file access.
- If your project is on a slow HDD or network drive, moving it to an SSD can make a huge difference.
- Also watch for cloud-sync folders like OneDrive/Dropbox if they’re interfering.
5) RAM pressure
- If the system is swapping, everything feels bad.
- Close memory-heavy apps, and check whether the IDE itself is using too much heap or is starved for memory.
- For large projects, 16 GB can be enough, but 32 GB is much more comfortable.
6) Antivirus / endpoint scanning
- Real-time scanning of source trees can seriously hurt performance.
- Add project directories and IDE cache folders to antivirus exclusions if your environment allows it.
7) GPU/UI rendering
- If scrolling, cursor movement, or window redraws are laggy, it may be UI rendering rather than analysis.
- Try toggling hardware acceleration in the IDE.
- Update graphics drivers.
8) Repo/workflow habits
- Massive generated files, vendored dependencies, and giant lockfiles can slow everything.
- Split monorepos when feasible.
- Avoid keeping hundreds of tabs open.
- Use project-specific configs so the IDE doesn’t scan everything all the time.
9) IDE settings
Look for settings like:
- “power save mode” / “battery mode”
- “background indexing”
- “semantic highlighting”
- “on-type formatting”
- “auto-save very frequently”
- “real-time spell check in comments”
10) If it’s still bad: profile it
- Most IDEs have built-in performance logs or a profiler.
- Look for:
- startup time
- indexing time
- typing latency
- memory usage
- specific plugins consuming CPU
Best first moves
If you want the fastest improvement, do these first:
- Exclude huge folders from indexing.
- Disable unneeded extensions.
- Make sure the project is on an SSD.
- Check RAM/swap usage.
- Add antivirus exclusions if possible.
If you want, tell me:
- which IDE you use
- your OS
- project size/language
- whether the slowness is typing, startup, indexing, or scrolling
and I can give you a more targeted fix list.