Doesn't scale well to multiple CPU cores about log4shell-finder

[HynekPetrak]

Added also —threads N argument for adjusting number of threads from command line

[HynekPetrak]

That's actually how it works. For each folder a number of threads is processing files in parallel. Try to show progress with --progress 1 argument. Once it get stuck run lsof (on Linux) to identify the problematic file.
Note I could not workaround zip-bombs. So it's better to skip them with --exclude-dirs argument. Also it's recommended to use --same-fs to avoid scanning mount points and rather list file system roots explicitly

[jachstet-sea]

Ah, okay, perfect then :) Thanks for the quick answer
I've checked with --progress 1 and it's not a single file that blocks it. It's the main thread that's constantly at 100% and worker threads come and go but no more than about 5 at a time or so.
Well, nevermind, system has been scanned, all good :)

[HynekPetrak]

@jachstet-sea If cpu is not utilized well enough, the i/o might be the bottleneck. I’m planning to do a bit more experiments and maybe delegate more work to threads, need to be empirically proven

[HynekPetrak]

Hi @jachstet-sea can you test current version from git? I was able to shorten run time by yet another 20% with the latest changes.