Very high CPU usage

[jonnyom]

Hey there, very impressed with this project, I've seen real improvements on code search.

However, I'm seeing elevated CPU usage across the various processes.
I'm running the tool in three separate repos (we work across the three in parallel)

Happy to help debug this as you need, but I don't see any debug traces / logs in the CLI.

Running this on a MacBook Pro M4 Pro chip with 24GB RAM

[DeusData]

Hey, thanks for noticing. I will dive deep into this ASAP. Maybe the auto-indexing is a bit too aggressive, should be fixable. Will update you here once a new release attempts to address this :)

[jonnyom]

Thanks a million @DeusData! Let me know how I can help

[DeusData]

This is addressed in v0.4.8:

Watcher polling reduced by ~5x:

• Base tick interval: 1s → 5s
• Per-project poll interval base: 1s → 5s (+ 1s per 500 files, capped at 60s)

This means git status (the primary change detection for git repos) runs roughly every 5-15 seconds instead of every 1-5 seconds. With 3 repos, that's ~0.2-0.6 git calls/sec down from ~0.6-3 calls/sec.

Please update and let us know if CPU usage improves:

codebase-memory-mcp update

Restart your editor session after updating.

Would love your feedback on the CPU impact with your 3-repo setup!

[jonnyom]

Awesome, thank you @DeusData! I'll update and let you know

[d-suman1]

Hi @DeusData ,

I'm still seeing this issue on v0.7.0.

I noticed that issue #45 was marked as fixed in v0.4.8 with the watcher polling changes, but in my environment I'm still observing unusually high CPU usage.

Has there been any additional work on this since then, or are there any recommended workarounds/configuration changes that might help reduce CPU consumption?

I'm happy to provide more details. I can also attach screenshots from Activity Monitor and any other diagnostics that would be useful for troubleshooting.

Thanks!

[mvalentinov]

[github-actions]

Thanks for the report! To move this forward we need a bit more so we can reproduce it ourselves:

• the codebase-memory-mcp --version you're on
• the exact steps or command you ran
• a public repo (or a small dummy snippet) that shows the problem — please don't paste proprietary code

Once that's here we'll pick it straight back up. Heads-up: issues left awaiting-reporter are automatically closed after a few weeks of silence, but a comment reopens the door anytime.