Is it just on my machine or does someone else has the same experience with performance getting worse and worse with each update?
rMBP10,1 running 15.7.1 + OCLP 2.4.1 performing fine here. I fired up a 3D app (sketchup 2017) to kick the GPU into life, AOK. Seems (to me) to run as fast as on the other (supported) Mac here, a macMini8,1 2018Is it just on my machine or does someone else has the same experience with performance getting worse and worse with each update?
Is the 15.6 KDK still being accepted, or is it to the point it's better to wait for an updated KDK? I know you're talking about beta releases, but still, there isn't even a beta KDK to match the update.Heads up, 15.7.2 is out, downloading it to a supported Mac mini for a test run.
I dunno yet, the OTA process stalled during the "preparing" step. Anyway, I'm installing it first on a supported Mac, so OCLP is not in play yet.Is the 15.6 KDK still being accepted, or is it to the point it's better to wait for an updated KDK? I know you're talking about beta releases, but still, there isn't even a beta KDK to match the update.
OK, was just curious. I don't do betas, but I also know the KDKs for anything other than Tahoe haven't been updated in a while, and that can be a concern if it goes too long.I dunno yet, the OTA process stalled during the "preparing" step. Anyway, I'm installing it first on a supported Mac, so OCLP is not in play yet.
OK, was just curious. I don't do betas, but I also know the KDKs for anything other than Tahoe haven't been updated in a while, and that can be a concern if it goes too long.
OK, As I've mentioned a few times, I use the USB method for updating, because the OTA method is unusable for me when having to manually apply patches after an update, because things are so slow. The USB method solves this as it applies patches as part of the process. I mentioned this to say, that I don't know what OCLP is doing during that time since it's the black screen with the Apple logo, and the progress bar. I know it's worked though because everything is working on reboot, and the patch date is updated, saying everything is applied.OCLP did not ask to update the KDK for SEQ it did update for T26 b2.
Update done. ota. 24G313 installed without any interventions. patched using 2.4.1. Not a big jump obviously from G309.Heads up, 15.7.2 is out, downloading it to a supported Mac mini for a test run.
@Kevo It looks like your Macbook Pro can go up to Catalina (natively.) The last time I checked, both Chrome, and Firefox still support it with the latest version(s)
OK, wasn't aware of Chrome's current support. This iMac 17,1 runs Monterey natively as the last supported OS, and then I have Sequoia on a second APFS Volume for things that require newer. I'm surprised they dropped Big Sur.FWIW, Firefox is still well-supported on Catalina.
Chrome dropped support for Catalina quite a while ago and currently requires Monterey or newer.
Hello, non problem a each update on Imac 2012.Is it just on my machine or does someone else has the same experience with performance getting worse and worse with each update?
Sounds like your Fusion Drive is evicting and loading cached files on each subsequent boot of macOS version. Your Fusion Drive SSD component is most likely 32GB. It kind of makes sense when each boot of macOS version manages the Fusion Drive. Fusion Drive is a software layer which makes the two different physical disks appear as a single disk. Apply some skepticism here, I could be barking up the wrong tree.Hey all, I've run into some slight issues toggling between my installed versions of macOS, and was hoping someone could give me some pointers on how to optimize things. Whenever I've been running in Monterey for a while, and reboot back into Sequoia things are extremely slow, for about 5 to 10 minutes after the initial reboot. Going the other way, Monterey is only sluggish for about maybe 2 minutes or so. Both are on the internal Fusion drive, and share the entire drive via APFS Volumes. Is there a way to optimize Sequoia's login process ? Loading the same stuff always seem slower on Sequoia than Monterey. Is there any part of OCLP I can disable, that might run at startup, that may not run under Monterey, as it's not needed? After things have settled down things are fine, and if I reboot Sequoia, without switching installs, things are fine as well. So I'm mainly asking if I can optimize load times between switching installs.
Mine is 128 GB, I have a 2 TB config. The 1 TB had the 32GB, the 2, and 3 TB have 128. You are probably correct though, and that was my thoughts as well, when switching between installs, the inactive parts were being moved to the standard HDD to make room for the most used stuff on the SSD. That part I understand, I was just curious about de-bloating Sequoia, so it's lighter like Monterey, or if OCLP did stuff on boot that I could disable since the system is patched, I don't need it to do anything right now, other than the boot loader.Sounds like your Fusion Drive is evicting and loading cached files on each subsequent boot of macOS version. Your Fusion Drive SSD component is most likely 32GB. It kind of makes sense when each boot of macOS version manages the Fusion Drive. Fusion Drive is a software layer which makes the two different physical disks appear as a single disk. Apply some skepticism here, I could be barking up the wrong tree.
When do I throw in the towel, and stop using Monterey period. It still works, and I can do my daily tasks, but more and more apps are dropping it to support future updates, and the only thing that doesn't work is Apple based DRM under Sequoia, for video in Safari, or prime app, etc, or downloading HD copies of iTunes stuff. I can stream iTunes content fine, and download an SD version to watch locally. Since I have an Apple TV, and a Roku, and a couple of Google based streamers, I really don't need the iMac for commercial content, and I have the iPhone too.Yes, it sounds like the Fusion Drive cache is swapping data.
It's basically a black box - the Fusion logic decides which files are accessed the most often and stores them in the SSD portion to accelerate performance. Having 2 operating systems is probably making it evict files from the previous operating system whenever you switch because the Fusion drive was never designed to run multiple versions of macOS on the same drive.
In the long run, it might be cleaner to run the other operating system (either the older or newer) on an external SSD out of the USB 3.0 or Thunderbolt 2 port and save the Fusion Drive for a single operating system or even just as a data drive (without OS).
There aren't any more native Thunderbolt 2 SSDs on sale, but you should be able to find Thunderbolt 3 or 4 SSD and they can run an adapter cable to your Thunderbolt 2 port, for example.
I have now tried it several days without the problem. Thanks again!I forgot to give you the complete command. It isBash:pmset -a standbydelaylow 86300