I think it’s much more likely that I/O syscalls on MacOS are the culprit of slowness than APFS. I don’t see any entries in the table against HFS+.
I think it’s much more likely that I/O syscalls on MacOS are the culprit of slowness than APFS. I don’t see any entries in the table against HFS+.
That would also match with the workaround of using a Linux VM (assuming that VM disk i/o is bypassing the relevant part of the darwin i/o subsystem)
node/npm operations are vastly slower for me on docker with a linux vm, I have tested this before.
APFS does suck though, don't get me wrong
edit: I just tested, 36s for an `npm i` on a decently large project I have locally, 46s with an overlay fs
Can also confirm. We’ve had some client projects that had npm inside of containers and those were horribly slow on macOS.
Not an overlay fs, a VM writing to its own virtual block device.
I should have been more specific, I tested with:
`rm -rf node_modules && docker run --rm -ti -v $PWD:/app node:20.19.0-alpine3.20 sh -c "cd /app && time npm i"`
So an overlay FS (if I'm understanding you/the OP correctly), not the VM's disk