-
Spotlight on QNAP 4.3.5
-
long story, but here it goes.
Years ago, I purchased a copy of OS X 10.6 from Apple on DVD.
I built a boot drive. I used this to clone other boot drive. I eventually updated my 10.6 boot drive to 10.6.8
10.7 came out. I took another empty drive, cloned it from the 10.6.8 drive, and now it was 10.7
I then cloned the 10.7 drive, and used that, but the 10.7 “clean drive” stayed in my closed, along with the 10.6.8 drive, which was used for cloning only.I have been following this process since then. When 10.13 came out, I made by clone of 10.12.6, and updated that drive to 10.13. That became my “master. I cloned that and used that clone of 10.13 (which eventually became
10.13.6). When 10.14 came out recently, I took out the 10.13 master, cloned it to another drive, updated it to 10.13.6, and then updated it to 10.14. Once I had the master 10.14 SATA drive, I cloned that to a 120 Gig SSD, which is now my “daily use” drive in my 2009 Mac Pro (which has been flashed to a 5,1 with updated boot firmware).
The tests I just showed with Mojave, the Sonnet 10G PCIe card, and the QNAP TS-1685 were done from that SSD.So it is a “fresh install” – well, its a clone from a clone dating back to a OS X 10.6 DVD, but yes, I guess it’s a fresh installation.
I just did a service call this past Thursday for a client that has a brand new iMac Pro, and was getting terrible performance with their Adobe software. I went over, and saw that their IT deparment simply migrated EVERYTHING from his 6,1 Mac Pro, without reinstalling anything or cleaning out anything. A new 1TB internal boot SSD was already almost 95% full after having the machine for 2 days. I saw every version of Acobe on it from 2014, 2015, 2016, etc. all the way to the lastest Adobe CC download. Tons of programs that were not being used, and my client has no idea of what most of the stuff in the Applications folder even was.I don’t know why people do this. Because they can’t be bothered reinstalling their software, year after year, after year – and going from computer to computer to computer. So when I saw the poor performance of this expensive new machine – well I understood instantly what was going on. Sometimes, if you don’t empty the garbage in your kitchen, your kitchen will start to stink !
Bob Zelin
Bob Zelin
Rescue 1, Inc.
bobzelin@icloud.com -
That is a great way/idea to migrate. For me, I don’t know if you recall, but I had a similar problem going from 10.12 to 10.13 and the only method that fixed it was fresh installing 10.13. So it was that fresh 10.13 install that I simply upgraded via App Store to 10.14, not years of garbage piled up. My SSD is always 60% empty in any case since I don’t want to kill it before it’s time. For now I have downgraded via fresh install and everything is running smoothly. I have this suspicion that upgrading via app store there is a bug that somehow limits SMB read performance. Have you had a chance to test the renaming of 1000+ files both in High Sierra and Mojave via SMB? Hint: Not a fun process in Mojave.
_
Passion and knowledge put to work
kronik.studio -
Hey Nick,
Same thing happen to us. Mojave seems to have poor SMB performance (or unstable I must say). We downgrade to High Sierra as well and everything was back to normal.
Can you confirm that a «Fresh install» of Mojave resolves the issue?
Thanks alot for this valuable info.
Best
Mel -
We just saw that Promise Sanlink2 rolled out a Mojave compatible update 2 days ago. We are using this component as well as TB adapters. Maybe it could be the Sanlink2 drivers and now it is resolved with this update.
Couldn’t be sure so we’ll wait before going back to Mojave
-
Hello,
Unfortunatelly for progress, but fortunately for my sanity, I will avoid upgrading to Mojave for a while, so I don’t have any feedback regarding performance under a fresh install.
Perhaps you’ll pioneer in that forefront?
Always with regards,
Nikos_
Passion and knowledge put to work
kronik.studio
Reply to this Discussion! Login or Sign Up