Bug Description
Not sure it is a bug, but definitely a defect or at least a subtle issue. Basic-memory is used as a mcp tool to gemini-cli in my setup. I noticed that it would constantly utilize quite a lot of CPU resources even when there is no input from gemini. I also use other MCP tools, and none of them have such a behavior.
One can find it out by looking at the htop screen.
Steps To Reproduce
Steps to reproduce the behavior:
- Install version '0.16.2'
- Setup basic-memory as a mcp tool to gemini-cli
- Open
gemini
- Check the
htop screen.
Expected Behavior
Expect that basic-memory is idle when there is no call from gemini-cli.
Actual Behavior
The background basic-memory process introduced by basic-memory mcp is constantly occupying 20-30% of CPU cycle on my computer.
Environment
- OS: [e.g. macOS 14.2, Ubuntu 22.04] WSL2
- Python version: [e.g. 3.12.1] 3.13.5
- Basic Memory version: [e.g. 0.1.0] 0.16.2
- Installation method: [e.g. pip, uv, source] uv
- Claude Desktop version (if applicable): n/a
- Gemini-cli version: 0.19.1
Bug Description
Not sure it is a bug, but definitely a defect or at least a subtle issue. Basic-memory is used as a mcp tool to gemini-cli in my setup. I noticed that it would constantly utilize quite a lot of CPU resources even when there is no input from gemini. I also use other MCP tools, and none of them have such a behavior.
One can find it out by looking at the
htopscreen.Steps To Reproduce
Steps to reproduce the behavior:
geminihtopscreen.Expected Behavior
Expect that basic-memory is idle when there is no call from gemini-cli.
Actual Behavior
The background basic-memory process introduced by basic-memory mcp is constantly occupying 20-30% of CPU cycle on my computer.
Environment