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.
Latest WebKit Builds Address Browser Scrolling Performance on Retina MacBook Pro Models
- Thread starter MacRumors
- Start date
- Sort by reaction score
The only thing I agree with you is about the "fullness" of Anand.
I understand perfectly well what I am taking about. You are right though that at native it's just rendered pixel doubled. But in any other scaled mode it's exactly as I decribed it. Let me remind you that the ACD at 30" has a 2560 × 1600, that's about 4 million pixels, in 1920x1200 (and to a lesser extent in 1650x) we are talking about (2x2=4 times) 9.2 million pixels for the video card to draw, and then operate the scaler down to retina resolution. That's two and 1/4 acds. If it's the "software" (and it's simple operations that prove that's not the case) then how come even after ml the ui lags and stutters have not been solved?
Wow, much better on my MBP without retina! Also seems to have fixed the rendering issues where you get a black line.
Definitly smoother.
This is one of the many updates still to come for the retina macbook pro
http://www.macpoint.be/thoughts-on-the-macbook-pro-15-inch-with-retina-display/
The only hardware issues the retina's have are image retention.
If I can play borderlands 2 at native resolution with high settings on this, I'm not thinking it's a hardware problem.
This is one of the many updates still to come for the retina macbook pro
http://www.macpoint.be/thoughts-on-the-macbook-pro-15-inch-with-retina-display/
The only hardware issues the retina's have are image retention.
If I can play borderlands 2 at native resolution with high settings on this, I'm not thinking it's a hardware problem.
Last edited:
Holy mother of God, I've been waiting for this news since the day I got my retina MacBook Pro. Safari for rMBP has been the single most crappy product they've ever released. It was so bad it's almost impossible to understand how they released it in the first place. Scrolling in sites like facebook and pitchfork was so bad I thought about returning the machine.
However, now that nightly has a fix, what are the chances of this being incorporated in the next Safari update? When do you guys think it will be released?
However, now that nightly has a fix, what are the chances of this being incorporated in the next Safari update? When do you guys think it will be released?
All of WebKit has nothing of KHTML in it. The QTWebKit port is being backported to KDE's structure and I would appreciate if people realized that for the past 5 years nothing from KDE has existed in any Apple WebKit code.
Installed. Instantly noticed a difference on Facebook, Neowin.net and Gizmodo/Lifehacker.
Im a happy man, it made my day! Choppy scrolling in Safari was the most annoying thing on my rMBP.
Im a happy man, it made my day! Choppy scrolling in Safari was the most annoying thing on my rMBP.
Damn the difference is incredible on my 2011 Air! In fact everything in the browser seems so much faster.
Hopefully Apple implements this into Safari soon. Scrolling full screen on my top-end 2011 27" iMac is horrible.
My wife, who knows little about computers, even asked me why a $2400 (I live in South Korea) computer couldn't even scroll down a webpage without choking.
My wife, who knows little about computers, even asked me why a $2400 (I live in South Korea) computer couldn't even scroll down a webpage without choking.
Because the software scalers probably aren't yet fully optimized at all. There's probably still a ton of operations left up to the CPU, not the GPU, so it's not fully using the pixel fill rate capability of the GPU and it's getting bogged down by the process scheduler.
Anyway it's moot, most people are not running the scaled modes, using plain old 1440x900 points (2880x1800 pixels) and getting this lag, so it's obvious there's something wrong with Apple's scaler in Quartz Extreme. Let's face it, HiDPI mode is quite new and it's not like Apple has ever been quick at optimizing their graphics stack (look at how long it took them for OpenGL 3.2..).
The GPU itself can do, again, way more than 2.32 GP/s. That's Gigapixels, billions of pixels per seconds. It's quite enough to run the resolution and do proper updating at 60 fps. Something else is amiss in the software stack where we're not getting done with a frame in less than 15 ms (the maximum render time per frame to maintain 60 fps).
I maintain this isn't a hardware problem at all.
For the last 5 years, WebKit has not been an Apple only project. Heck, 2 years ago, Google surpassed Apple in terms of raw commits to the code base. Of course WebKit has evolved since its days as KHTML, it still is a fork of KHTML, and is maintained by quite a few folk outside of Apple. In fact, Apple aren't even the main contributors anymore.
Thats all fine, but google keeps a lot of its top improvements in their forked chrome project while everything apple does is available to benefit everyone.
So I just installed the latest build.
Holy crap.
I actually thought Safari behaved pretty well and never had any complaints about scrolling performance, but now my rMBP performs better than any of my other computers in heavy sites like The Verge and Facebook.
And I only have the lowly HD4000.
I hope this makes it into a Safari update!
Oh yeah, it's totally a hardware problem.
Holy crap.
I actually thought Safari behaved pretty well and never had any complaints about scrolling performance, but now my rMBP performs better than any of my other computers in heavy sites like The Verge and Facebook.
And I only have the lowly HD4000.
I hope this makes it into a Safari update!
Oh yeah, it's totally a hardware problem.
They unfortunately do what all tech companies seem to do. Push out products to the public that are not ready; keeps the profits going. The public is part of the testing ground more frequently now.
I sure hope Apple rights this boat and doesn't end up like Microsoft, Dell, HP, Cisco, etc.
If you are reading this Apple, I sent my 13" rMBP back because of the scroll lag. When you get it fixed, I'll be buying it again but not until then.
People here are missing the point. This only fixes the issue for some websites.
- The Verge is still choppy as are many other websites.
- Webkit crashes in double tap mode.
- Webkit slows down the UI frame rate (it's measureable). And no, it's not a memory leak. I did all the tests for that.
Bottom line: not ready for prime time.
- The Verge is still choppy as are many other websites.
- Webkit crashes in double tap mode.
- Webkit slows down the UI frame rate (it's measureable). And no, it's not a memory leak. I did all the tests for that.
Bottom line: not ready for prime time.
I'm pretty sure I remember reading somewhere that Chrome forces the discrete GPU to fire up (which gives smoother results at the cost of battery life) whereas Safari uses the integrated Intel 4000HD, which is why it was struggling.
You make a very convincing argument.
But what if in a typical apple fashion they aim to not optimize the code but offload it to better hardware next year?Once all the images are loaded (by scrolling once down the entire page) The Verge seems fine for me. I still get some hiccups as images are loaded.
Of course it's not ready for prime time, these are just nightly builds, not Safari release candidates. It does illustrate what can happen when software is optimized.