I had to shake that "the company must fix this!!" crap when I realized that almost all cutting edge software is put together with Scotch tape and gum these days and that I needed to learn how the tech works before being able to solve these problems.Eddy into Spotlight’s search field and pressed Return…and it took Spotlight well over a minute to finish its search. I've been here brother, so I know exactly the mindset you're in. You act like anybody not holding your hand through this just hasn't done the work, when in fact we have, and are tired of it, and you are just ignoring the experience of the people YOU ASKED for help! Alternating between yelling at their support that it "should" be a certain way and yelling at us that it "should" be this or that will get you squat. How much clearer can I be? Maybe of you don't understand these reasons and consider them muttering, you simply are in over your head? You need to gain some deeper knowledge on these technologies if you hope to solve this. Spotlight wasn't written for network protocols. The on-disk database holding that index is built to perform on a local drive, not a networked one. The file permissions needed are a unique setup to Spotlight that aren't supplied over SMB. the technologies are not built for each-other. If you think you're the hotshot that will solve this for the masses of us who have worked around it for years. Barring any network bottlenecks (which you seem to be claiming shouldn't be a problem). Try some type of NFS setup which will identify itself as a local filesystem to your Mac, therefore letting you to theoretically index it normally. You're up against corporate behemoths fighting in their huge sandbox.
Switch to a different file sharing protocol. They've been incredibly disruptive, unstable, surface-level and again, mostly centered around marketing. Which is kinda true if you know the deep history of Apple's major backend changes over the past 10 years, or the history of technologies like SMB and how Apple begrudgingly adopts it without adapting their proprietary technologies to it. Therefore, according to them, you're ridiculous for even expecting it. They've never advertised it to you as working on a network drive. It works for grandpa and grandma on their local hard drives. You're dealing with wherever the wind takes Apple. If you're gonna be a sysadmin for a Mac environment you need a reality check. Oh, wait.įirst of all, you pay the same pricetag as anyone else. Just leave something on Apples issue tracker, I'm sure they'll get right back to you. This seems terribly broken to me, though. My current plan is to build an automator functionality to search.
I am assuming that the native share off Catalina is already optimized for mac/mac communications. I have tried the vfs_fruit extensions on the NAS, no effect. We're willing to purchase a mac server, anything, to try and fix this. Is there a way to have a central repository of files, shared to multiple mac users, and have the finder search return quickly with a scan of the directory names, like ls | grep does in the terminal? I can see the problem on a share hosted from a Catalina client, as well as shares on our NAS. If the same search is done in the terminal with ls | grep it's basically instant.Ĭan anyone help suggest a solution to this problem? My users want to use Finder as their workflow, not a third party alternative. Searching in Finder is VERY slow, several minutes to check a few thousand files. The problem I have is with searching them on a OSX client. The latest OSX release appears to have fixed the slow browsing problem on SMB shares.
0 kommentar(er)
