←back to thread

MacOS Catalina: Slow by Design?

(sigpipe.macromates.com)
2031 points jrk | 5 comments | 22 May 20 15:39 UTC | HN request time: 0s | source
1. zimpenfish ◴[22 May 20 16:20 UTC] No.23273728[source]▶
Their "see!" shell script example is a bit rubbish because I get 0.012s, 0.005s on this Mac laptop whilst getting 0.022s, 0.023s on Linux box 1 and 0.006s, 0.006s on Linux box 2.

Changing the filename to test2.sh on the Mac (which should trigger the delay, right?) gets 0.006s, 0.006s.

I don't think the shell scripts are doing what they claim (and wouldn't the second run be faster anyway because of caching?)

replies(1): >>23273858 #
2. egorfine ◴[22 May 20 16:30 UTC] No.23273858[source]▶
If they are caching based on inode, this will not invalidate the cache. Do cp test.sh test2.sh and try again.
replies(2): >>23274069 #>>23274453 #
3. saagarjha ◴[22 May 20 16:46 UTC] No.23274069[source]▶
I feel like cp might do an APFS CoW and this might still cause problems…
replies(1): >>23274422 #
4. ken ◴[22 May 20 17:10 UTC] No.23274422{3}[source]▶
No, even "cp -c" creates a new inode.
5. zimpenfish ◴[22 May 20 17:13 UTC] No.23274453[source]▶
Sorry, when I said "changing the filename to test2.sh", I meant in the commands run, not `mv test.sh test2.sh`. i.e. I have both `test.sh` and `test2.sh` in `/tmp` now.