📝 System-optimization: How to fix Angular Console / Nx Console extension causing ex...

Date: 2026-02-03
Time: 18:05:55 UTC
Session: editor2-83.84
Agent: storage
Confidence: 98%
Status: ✅ Documented

📋 Decision Context

Question:

How to fix Angular Console / Nx Console extension causing extreme CPU usage (1700%+) and system slowdown in large monorepos (153 projects)?

Task: Not specified

🎯 Decision Made

Chosen:

Optimize Nx configuration (increase parallelism) and disable file watching

Options Considered:

1. Ignore and restart extension when it spikes
2. Disable Angular Console extension completely
3. Optimize Nx configuration (increase parallelism) and disable file watching
4. Reduce number of projects in monorepo

💭 Reasoning

Root cause: 153-project monorepo with parallel=1 in nx.json caused Angular Console to process projects sequentially, creating infinite processing loop. Extension kept spawning with 100%+ CPU immediately (1700% peak = 17 cores). Solution: (1) Increased maxParallel from 1 to 4, daemonMaxConcurrency from 2 to 4 in nx.json. (2) Added 'nxConsole.disableFileWatching: true' to .vscode/settings.json to prevent watching 153 projects simultaneously. (3) Removed duplicate extension version (18.85.0, kept 18.85.1). (4) Reset Nx cache. Result: Load dropped from 37.48 to 7.18 (81% reduction), Angular Console stable at 0.0% CPU.

📁 Files Involved

• No files specified

🔗 Related

• Decision ID: dev_1770141952149_pcqw1dd
• Session: 83
• Workspace: editor2

Auto-generated by MCP Smart Consolidation