Lion was quite a nice-looking OS, I'll give it credit for that. Though annoyed about its lack of PPC-compatibility, I do remember using a lot of Mountain Lion back in the day, and it still felt like a serviceable OS. Mavericks is when I lost touch.
Lion was quite a nice-looking OS, I'll give it credit for that. Though annoyed about its lack of PPC-compatibility, I do remember using a lot of Mountain Lion back in the day, and it still felt like a serviceable OS. Mavericks is when I lost touch.
The Marble interface of Lion, replacing Aqua, was originally slated to roll out with Snow Leopard. Reports at the time of the developer preview betas, particularly from January 2009, made mention of Marble as an expected feature of the then-upcoming SL release.
Ultimately, it was pushed back to Lion.
Sorry, this sentence made me chuckleIts far more stable and crappy than I remember.
I have to say that I did find it less than an optimal UX under Mojave with constant beachballing before slowly loading a webpage. It wasn't unusable but just unresponsive enough for me to not want to persevere with macOS on it.
That was with dosdude's patcher. I don't know if OCLP would provide any additional optimisations to make Catalina work better but I might give it a go. As of now, it runs Chrome Flex quite well but I already have a Chromebook with much better battery life so it's just sitting there.
Nope. OCLP starts with Big Sur, so the patcher is all there is. Older version of OCLP may have worked with Catalina but even the OCLP developer strongly suggests to use the DD1 patcher with Mojave and Catalina. As of now, it is running Snow Leopard and is as snappy as it can be with that.Did you try out tinkering with OCLP in the end?
Bit off topic here, but what are your thoughts on Picard S3? I've watched the first 5 (Ep 6 isn't available yet) and it has been really good. Seems like with Terry Matalas in a much bigger role, things are going much better.This is most peculiar - my 2010 C2D MBA outdoes my 2011 i5 MBA in video playback performance with Amazon's VOD service. Attempting to watch its content on the latter is almost impossible due to sluggishness and stuttering.
![]()
I'm wondering if it's because the MBA is running the latest version of Firefox under Catalina (as shown above) - and enjoys improved support in this field whereas the MBP is on 102.9.0 Extended Support Release with High Sierra.
![]()
Or perhaps the GeForce 320M has an advantage over the HD 3000 in some form?
![]()
![]()
I'd be interested in your comments, my fellow Club 11 members.![]()
This is most peculiar - my 2010 C2D MBA outdoes my 2011 i5 MBA in video playback performance with Amazon's VOD service. Attempting to watch its content on the latter is almost impossible due to sluggishness and stuttering.
![]()
I'm wondering if it's because the MBA is running the latest version of Firefox under Catalina (as shown above) - and enjoys improved support in this field whereas the MBP is on 102.9.0 Extended Support Release with High Sierra.
![]()
Or perhaps the GeForce 320M has an advantage over the HD 3000 in some form?
![]()
![]()
I'd be interested in your comments, my fellow Club 11 members.![]()
May also have something to do with the patchers as hardware acceleration can be buggy sometimes, might be worth trying High Sierra to see how it performs. Could possibly be a bit better on a native OS.Then again, it would also be worth investigating whether video decoding is handled by hardware or software on both, and whether it’s the CPU assigned to the work or the GPU.
May also have something to do with the patchers as hardware acceleration can be buggy sometimes, might be worth trying High Sierra to see how it performs. Could possibly be a bit better on a native OS.
How much could that affect video performance though? Are there any hardware video encoding variables inside it?The other thing I’d ponder is whether the prefs.js for each FF build have the same settings, optimizations or not, throughout.
How much could that affect video performance though? Are there any hardware video encoding variables inside it?
The 320M is likely just more powerful than HD3000 in some respects.
View attachment 2177804
Of course some benches show an advantage for the 2011s, so it may have depended on whether the games were CPU or GPU bound.
View attachment 2177805
As for the VRAM comment, my 2011 MBA has 4GB (and accordingly assigns 384MB to the GPU) but it's also the i7, so that may pose an issue for a comparison, but I'm willing to look at it if needed. It's also just running 10.13.
Bit off topic here, but what are your thoughts on Picard S3? I've watched the first 5 (Ep 6 isn't available yet) and it has been really good. Seems like with Terry Matalas in a much bigger role, things are going much better.
I see you're only at Ep 1, so I won't go spoil anything here, but it gets even better the further the plot unfolds![]()
What resolution is it running at? The 11" is 768p if I'm not mistaken, so 720 then?
Not sure how well the 320M does with modern video streaming, with offline content I've found 720p runs quite well on it. I think in some cases the 320M does outperform the 3000, but then IIRC the HD 3000 in the 11" only has 256MB compared to the 512MB on my MBP.
Not a Club 11 member (yet), but…
The thing I’d test, if it were possible (and one wanted to futz with it) is to have a partition on the 2011 which meets the same 10.15/FF110 specs and running a side-by-side on the same video (assuming the RAM for both are in the same neighbourhood). Off-hand, it doesn’t make sense that there would be such discrepancy even if the HD 3000 was a step back from third-party GPUs. Then again, it would also be worth investigating whether video decoding is handled by hardware or software on both, and whether it’s the CPU assigned to the work or the GPU.
Beyond that, I honestly don’t know.
If I read @TheShortTimer ’s description correctly, the patched 2010 MBA with the GeForce 320M running FF110 on Catalina is the one doing well with the video, whereas the un-patched 2011 with iGPU running FF102ESR on High Sierra is the one having trouble here.
The other thing I’d ponder is whether the prefs.js for each FF build have the same settings, optimizations or not, throughout.
The only working hypotheses I have are there were video decoding improvements made to the very latest version of Firefox; there are optimizations manually different with one prefs.js versus the other; or else the OpenCore configuration for the GeForce 320M on the C2D is really remarkable.
Beyond that, I have no ideas.
That's a good idea but I'd need to free up some HDD space on the 2011 MBP before I could install Catalina - or purchase a larger HDD... I could also run this test with my 2011 i5 MBA which uses the HD 3000 as well and currently has High Sierra installed.![]()
I could see what happens if I switch to FF111 on the MBP but I'd probably need to get rid of FF ESR because I've seen in the past that things become very messy when you have two iterations of the browser installed...
Hold up… is the MBP running from a rusty spinner or solid state?
As a safeguard, duplicate the profile directory for a fallback. The slightly annoying thing about the way FF handles profiles, via the .ini, makes it impossible to have two profile directories with different randomized-character names, and each version of FF referring to discrete .ini files on which profile to use at launch.
A spinner but hardly rusty.
![]()
With the assistance of a eGPU, I can play 4K UHD files on the MBP from the HDD so that's not the culprit. If anything, it makes the problems with Amazon and Firefox ESR all the more perplexing.
Thanks - I'll do that.The usage of FF ESR is a legacy to when I ran Snow Leopard on my MacBook 1,1 and it was among the handful of browsers that still supported the OS. Whilst there is the obvious benefit from long-term support for older operating systems (like High Sierra) the downside is that it's several generations behind the main version of FF in terms of the improvements and optimisations that you speculated are at play.
Second this.I don’t wanna be that annoying MR forums member, but that HDD is your bottleneck.
Not even a 7200rpm PATA HDD could hold a candle to a DRAM-less, budget mSATA on my iBook clamshell G3 with ATA-3 protocol of ~25MB/s! In other words: that 7200rpm HDD can’t saturate a SATA III 6Gbps bus, but an SSD with a DRAM cache, like on a WD Red or Blue SATA SSD, can (yes, I’m using one of each in different Intel machines). And for streaming movies, that cached stream is going to need all the speed you can throw at it.
Second this.
I've had both super cheap, DRAM-less SSD's and new 7200rpm spinners in my A1212 (17" Late 06), and the difference is crazy! While boot up times aren't as different as 4200/5400 to SSD, when you get to the desktop, the SSD machine is ready to open apps right away while the spinner takes a minute or two to launch them.
General tasks also felt noticeably slower on the HDD compared to the SSD, videos (both online and offline) were just laggy enough to be an annoyance. The SSD was the singular upgrade that has uplifted performance on every machine I own. These days, every Intel machine of my has an SSD in it:
A1398 (2015): WD SN570 1TB (it was upgraded to a proper NVMe SSD from a 256GB SSUBX)
A1278 (2011): Crucial MX500 500GB
A1342 (2010): Kingston A400 240GB
A1278 (2009): SanDisk SSD Plus 240GB
A1186 (2007): Kingston A400 240GB
A1212 (2006): Crucial MX500 500GB
The MX500s are really good drives, they have DRAM cache and are extremely fast (for a SATA3 drive). I swear by them. The A400 and SSD Plus are cheaper, DRAM-less drives that are used in my machines that I use less often and/or need an SSD but don't require a high-end drive.
I can say now that the singular reason why the 2010 MBA is faster is because it has an SSD.
...which makes me slightly sad that 320M Macs never went beyond 2.66 GHz. There was a 2.8 GHz P9700 if the 3.06 GHz T9900's TDP would have been too much for the machines in question (2010 13" MB/MBP; MM). Curiously, Notebookcheck lists an Acer laptop that supposedly shipped with the 320M... and a Nehalem, despite the chipset being for Core 2 Duo only. Probably just a typo (there's a discrete GT 320M as well), or... *x-files theme*The 320M is likely just more powerful than HD3000 in some respects.