4 ms·
A few versions of MacOS ago, I noticed that mounting a network drive with NFS through the GUI (e.g. Command K) took far longer than it should; 15 to 20 seconds
by mcpackieh 3y ago
A few versions of MacOS ago, I noticed that mounting a network drive with NFS through the GUI (e.g. Command K) took far longer than it should; 15 to 20 seconds when it should have been nearly instant. And in fact if I had a terminal open when I did it, I could see that the drive was mounted and accessible in a veritable instant, while the GUI progress indicator just sat there for another 20 seconds. I never bothered to dig into it, but I presume it was waiting to stat all the files in at least the first level of sub-directories (more would have taken much longer, so it certainly wasn't doing the whole drive recursively.) I can't imagine any sane reason to delay showing the user the root directory of the mount before stating files in the sub-directories, but I also can't imagine any other quasi-legitimate reason it could have been taking so long.
- dragonelite 3y agoI heard a story a while ago that some apps just create a fake progress bar/indicator. Because if it happened instantly people don't trust/believe the action actually happened.
- hnbear 3y agohttps://www.theatlantic.com/technology/archive/2017/02/why-some-apps-use-fake-progress-bars/517233/ https://www.theatlantic.com/technology/archive/2017/02/why-s... But I doubt that’s happening here. Anyone mounting NFS drives via a direct path in cmd-K isn’t shocked it’s quick.