[Bug]: High CPU/disk usage when indexing large generated data folders
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- performance, search
Research direction
No file or test is named in the issue. Start by reproducing the sustained CPU and disk usage on Windows with fff-mcp while indexing a large generated folder, then trace the indexing entry point and measure which work persists. Done means large or excluded folders no longer cause prolonged slowdown, with a clear way to identify or limit indexing work.
Written by the indexing model from the issue text.
Description
Which fff frontend?
MCP server (fff-mcp)
has logs
No response
Description
fff-mcp caused sustained high CPU and disk usage on Windows after it encountered a large generated data folder with many files.
After quitting/disabling fff-mcp, system performance returned to normal.
Expected behavior:
- Large/generated folders should not cause prolonged system slowdown.
- Indexing should be throttled, skipped, or easy to exclude.
Suggested fixes:
- Add folder exclusions.
- Auto-skip very large/high-file-count folders.
- Limit concurrent indexing work.
- Show which path is currently being indexed.
- Dominant language
- Rust
- Stars
- 11.2k
- Forks
- 473
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 32
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dmtrKovalenko/fff
-
triaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dmtrKovalenko/fff#842 · 2 comments ·
Maintainers usually reply within 3 days
-
[Bug]: zlob walker ignores `.git/info/exclude`Possibly taken @gustav-fff claimed this 1 day ago. Opentriaged
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dmtrKovalenko/fff#982 · 1 comment ·
Maintainers usually reply within 3 days
-
triaged
Difficulty 3/5 1-2 days Newbie friendliness 68/100
dmtrKovalenko/fff#980 · 1 comment ·
Maintainers usually reply within 3 days
-
[Bug]: pi-fff blocks session startup while indexing filesPossibly taken @adonis0147 claimed this 4 days ago. Openduplicate triaged
Difficulty 3/5 1-2 days Newbie friendliness 70/100
dmtrKovalenko/fff#975 · 1 comment ·
Maintainers usually reply within 3 days
-
[Bug]: on a non-git base path, the watcher indexes new files in hidden folders that the scan skips (0.11.0)Possibly taken @gustav-fff claimed this 6 days ago. Opentriaged
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dmtrKovalenko/fff#972 · 2 comments ·
Maintainers usually reply within 3 days
All issues in dmtrKovalenko/fff
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libnativeapi/nativeapi#21 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
longbridge/nsh#804 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day