Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Finder slow to show large folder contents - "loading"
- Thread starter HDFan
- Start date
- Sort by reaction score
It looks to be fixed in 14.7. But, I've gotten fooled on this before, so I hesitated to comment.
I'm too chicken to try Sequoia yet. Maybe in a month or two, like I did with Sonoma. Of course, Apple did do that funny forcing of the Sonoma upgrade which was why I changed as early as I did.
I'm sounding very cynical, I know. But, my experience hasn't been entirely positive.
I'm too chicken to try Sequoia yet. Maybe in a month or two, like I did with Sonoma. Of course, Apple did do that funny forcing of the Sonoma upgrade which was why I changed as early as I did.
I'm sounding very cynical, I know. But, my experience hasn't been entirely positive.
Not fixed for me on 14.7
A folder with 10,000 items took almost 15 minutes to open and display.
I'm happy for those who've apparently had the issue fixed, but the fix clearly isn't universal.
I look forward to being disappointed by Sequoia in the near future.
A folder with 10,000 items took almost 15 minutes to open and display.
I'm happy for those who've apparently had the issue fixed, but the fix clearly isn't universal.
I look forward to being disappointed by Sequoia in the near future.
I should've hesitated even longer.
The ~5000 item folder I tested just after upgrading to 14.7 did come up really quickly right after the upgrade. Today, after about five days of not testing, it's probably worse than at any time in the past. Of course, once I opened it once, it now opens very quickly. Just as before.
So, no better I'd say. Probably worse.
I probably could've hastened things up by clearing some caches as I did before. Then, this same folder would populate in a few seconds after the cleaning. Over time, probably after some other large folders get added to the cache it'd slow down again.
You'd think that a few lines of code, such as:
Has this folder been opened recently? If not, just open from scratch - never mind the cache.
would fix the problem. But, I guess this is why I don't work at Apple. I'd actually try to make stuff work, rather than tell whoppers about the reality and deny what's before everybody's eyes.
Wanna bet that by a month from now, this will get blamed on AI?
The ~5000 item folder I tested just after upgrading to 14.7 did come up really quickly right after the upgrade. Today, after about five days of not testing, it's probably worse than at any time in the past. Of course, once I opened it once, it now opens very quickly. Just as before.
So, no better I'd say. Probably worse.
I probably could've hastened things up by clearing some caches as I did before. Then, this same folder would populate in a few seconds after the cleaning. Over time, probably after some other large folders get added to the cache it'd slow down again.
You'd think that a few lines of code, such as:
Has this folder been opened recently? If not, just open from scratch - never mind the cache.
would fix the problem. But, I guess this is why I don't work at Apple. I'd actually try to make stuff work, rather than tell whoppers about the reality and deny what's before everybody's eyes.
Wanna bet that by a month from now, this will get blamed on AI?
still working in Sequoia? (fingers seriously crossed). Anyone else tried?
Me too, but I think I'll upgrade my laptop -- that way I can test Finder on the same external thunderbolt bay that's attached to the Studio.
Of course my small rural ISP is up to its usual shenanigans and nothing's working right. The Sequoia download is estimated at one day. I love living in the woods but holy crap it's hard to get decent internet here.
Note 2024 10 02. Haven't been able to download Sequoia -- it always fails, thanks to my rotten connection. I'll have to go to town and find a better connection.
Last edited:
I definitely need to wait for some of my software to be supported by it fully and make sure others are really seeing the problem gone and then without a doubt I will be upgrading. Hope everyone posts about their experience with Finder/large folders and Sequoia. I have seen hints of success before (too many times) only to have had my hopes dashed.
Correction: It's not totally fixed. Opening a directory in the finder is much faster. When in an app specifying a directory to open or save a file is as slow as before.
After my horrible ISP issues were resolved, I installed Sequoia on my Studio. I'm sorry to say that nothing has changed for me -- opening a folder with many images is just as slow as it was on Sonoma. I'm very disappointed.
Forklift, as always, opens the same folder and shows all images immediately (even if it's the app that spins up the thunderbolt-connected disks).
Resurrecting an old thread!
I've upgraded to Sequoia 15.6 and I experienced the same symptoms as mentioned here...
Finder is very slow to display files within folders on a 3TB SSD Raid made up of 3x 1TB mSATA SSD and a NAS.
Forklift ver 3 shows these files instantly. As does Forklift 4.
I tried to troubleshoot the issue and used Onyx to clear caches etc but to no avail.
My solution is to use Forklift 4.
I've upgraded to Sequoia 15.6 and I experienced the same symptoms as mentioned here...
Finder is very slow to display files within folders on a 3TB SSD Raid made up of 3x 1TB mSATA SSD and a NAS.
Forklift ver 3 shows these files instantly. As does Forklift 4.
I tried to troubleshoot the issue and used Onyx to clear caches etc but to no avail.
My solution is to use Forklift 4.
What I find strange is, Finder on my 2018 mac mini is very slow 30+ seconds to list all the files on my external thunderbolt HDD (OWC Thunderbay 4). Terminal is instant.
However, if I use Finder from another mac over the network (1Gbps) - the file list also appears instantly.
However, if I use Finder from another mac over the network (1Gbps) - the file list also appears instantly.
It looks like the problem is HFS+. I still haven't reformatted mine as APFS, both because in theory it's not optimized for spinning rust, and because I can't be bothered to take 3 TB off this and back (maybe one day...), but there are multiple reports in other threads and forums that it's the solution.
Apparently Apple considers HFS+ legacy at this point and can't be bothered to check if the new OSes broke it (much like they don't seem to care that 2.5 GbE USB adapters are limited to 1.9 since Sequoia, despite multiple reports: you want your full 2.5, you toss that dongle away, even though it worked perfectly before Sequoia, and replace it with a 5 GbE one.)
Apparently Apple considers HFS+ legacy at this point and can't be bothered to check if the new OSes broke it (much like they don't seem to care that 2.5 GbE USB adapters are limited to 1.9 since Sequoia, despite multiple reports: you want your full 2.5, you toss that dongle away, even though it worked perfectly before Sequoia, and replace it with a 5 GbE one.)
In Sequoia, I still get long loading times on spinning hard drives whether the drive is formatted HFS+ or APFS.
I don't know if anybody is still following this, but...
First, if anybody wants to see about the system here, check back to this post:
Earlier System Description
Since that time, the Studio macOS version has been updated several times and now is running on the latest version of Sequoia. (Yes, I am 🐔 about changing to Tahoe - I couldn't find even one feature that I imagine using in Tahoe that isn't already available in Sequoia or from an available third party app.)
Anyway, a couple months ago I got really tired of the spinning drives in the RAID box, umm, spinning all the time. Very annoying, plus probably not great for the drives themselves. After some research, including asking the SoftRAID people, it appeared that the issue was Spotlight indexing the drives. Over and over. And over. Not an unusual problem, apparently.
So, I tried the various solutions such as deleting Spotlight databases, reindexing, and so on. They all helped - maybe there was half the audible indexing. But, still annoying.
Fast forward to two weeks ago. I couldn't take it no mo. So, I prevented Spotlight from indexing the three volumes in the RAID drive. That seemed reasonable. I almost never use Spotlight to find files on these volumes. There's no system files on these volumes, so that isn't an issue. I left Spotlight indexing active for the internal Studio drive and the external Time Machine backup drive, which is an APFS formatted SSD.
That certainly stopped the incessant churning. I found a good app that will search for any files I need on these RAID volumes, if needed:
EasyFind
OK, what does that have to do with the subject of this thread?
I noticed a couple days ago that when I went to look at a large folder, the results came up very quickly. As in, a couple seconds. Much like the good ole Mojave days. I've tested this since, and it seems to be holding. (That could change this afternoon - who knows?) More than 5000 files in about 4 seconds - instant after it's been opened once. (An Onyx system maintenance resets that, of course.)
I'm not saying that this solution would work for everybody, but so far it's been really good for me. In fact, I even removed Spotlight from the Menu Bar. I haven't missed it. My goal wasn't to speed up reading large folders in the RAID system, but I won't complain that it seems to work. At least for the past week or so.
~~~
An alternative, that I've been too lazy to try implementing, might be a launchd script that turns Spotlight indexing on for these volumes at some arbitrary time, like 3AM, and when complete turns the indexing function off again until the next morning. That's for somebody more skilled and ambitious than I am.
First, if anybody wants to see about the system here, check back to this post:
Earlier System Description
Since that time, the Studio macOS version has been updated several times and now is running on the latest version of Sequoia. (Yes, I am 🐔 about changing to Tahoe - I couldn't find even one feature that I imagine using in Tahoe that isn't already available in Sequoia or from an available third party app.)
Anyway, a couple months ago I got really tired of the spinning drives in the RAID box, umm, spinning all the time. Very annoying, plus probably not great for the drives themselves. After some research, including asking the SoftRAID people, it appeared that the issue was Spotlight indexing the drives. Over and over. And over. Not an unusual problem, apparently.
So, I tried the various solutions such as deleting Spotlight databases, reindexing, and so on. They all helped - maybe there was half the audible indexing. But, still annoying.
Fast forward to two weeks ago. I couldn't take it no mo. So, I prevented Spotlight from indexing the three volumes in the RAID drive. That seemed reasonable. I almost never use Spotlight to find files on these volumes. There's no system files on these volumes, so that isn't an issue. I left Spotlight indexing active for the internal Studio drive and the external Time Machine backup drive, which is an APFS formatted SSD.
That certainly stopped the incessant churning. I found a good app that will search for any files I need on these RAID volumes, if needed:
EasyFind
OK, what does that have to do with the subject of this thread?
I noticed a couple days ago that when I went to look at a large folder, the results came up very quickly. As in, a couple seconds. Much like the good ole Mojave days. I've tested this since, and it seems to be holding. (That could change this afternoon - who knows?) More than 5000 files in about 4 seconds - instant after it's been opened once. (An Onyx system maintenance resets that, of course.)
I'm not saying that this solution would work for everybody, but so far it's been really good for me. In fact, I even removed Spotlight from the Menu Bar. I haven't missed it. My goal wasn't to speed up reading large folders in the RAID system, but I won't complain that it seems to work. At least for the past week or so.
~~~
An alternative, that I've been too lazy to try implementing, might be a launchd script that turns Spotlight indexing on for these volumes at some arbitrary time, like 3AM, and when complete turns the indexing function off again until the next morning. That's for somebody more skilled and ambitious than I am.