objective-see / objective-see/BlockBlock
Large impact on fs read speeds on M1 mac
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 848
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
First, thanks for a great product!
Support question: I'm seeing a large impact on fs read speed on a new M1 Pro, compared to my old 2015 iMac.
ls without BlockBlock on M1: 0.003, with BlockBlock: 0.015–0.090; this is with an empty rules-list
No diff in speed on the iMac.
Is this a known issue?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the reported ls timings on an M1 Mac with BlockBlock enabled and an empty rules list, then compare them with BlockBlock disabled and the 2015 iMac results. Trace the filesystem monitoring path to identify the source of the overhead; done means the read-speed impact is understood and the benchmark improves without changing the reported protection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, objective-c
- Domain
- operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100