80MB/s persisted disk scan #46256

Activity

1. github-actions

   assigned

   neriousy

   on Aug 30, 2026
2. github-actions commented on Aug 30, 2026

   

   github-actionsBot

   on Aug 30, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • opencode serve pegs CPU at ~1000% — fff content-indexes entire $HOME (search.ts enableHomeDirScanning/FsRootScanning) #32511: fff content-indexes entire $HOME / project root, causing sustained high CPU and massive disk reads — same root cause (fff scanner walking and content-indexing a very large directory tree)
   • watcher.ignore never reaches the embedded fff engine — per-dir inotify watches on every indexed dir (192K watches / 4.5GB RSS on a large root); root .ignore file is the only effective channel #37740: watcher.ignore never reaches fff engine — on large workspaces this results in 192K inotify watches and multi-GB RSS, same scanning behavior
   • [FEATURE]: Limit the directory scan depth. #36053: Feature request to limit directory scan depth — raised for the same reason (large AOSP source tree causing heavy disk I/O)

   The workaround mentioned in #32511 may help while this is being investigated:

   OPENCODE_DISABLE_FFF=1 opencode ...
   

   This disables the fff file-search engine and falls back to ripgrep, skipping the aggressive content-indexing scan. Placing a .ignore file at the project root (as described in #37740) is another option to prune what fff indexes.
3. octo-kumo commented on Aug 30, 2026

   

   octo-kumo

   on Aug 30, 2026

   Author

   More actions

   OPENCODE_DISABLE_FFF=1 does solve the read problem, is there an global option to disable it?
4. SeeleVolleri commented on Sep 8, 2026

   

   SeeleVolleri

   on Sep 8, 2026

   More actions

   I have the exact same issue.
   This is Nonsense function! Why the hell it tries to scan all my files especially it's aosp?!

   
5. thdxr commented on Oct 11, 2026

   

   thdxr

   on Oct 11, 2026

   Member

   More actions

   Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.

   — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
6. thdxr

   closed this as not plannedon Oct 11, 2026