Why does my rMBP suck on certain pages?

[Xgm541]

No! It is not about pixels. For the one site I've seen clear slowdown on (EBay new design page in Chromium a month or so ago), connect TWO external monitors so total number of pixels is >9million and scroll the page on the external -- no stutter. The number of pixels is irrelevant. In Chrome (because the bug tracker report was posted), it was because images were not being properly cached in HiDPI mode, and Safari was/is likely a similar bug.

retina display -> hidpi mode -> safari lags. Conclusion: it's the resolution.

 

[Aspen]

I have 16gb of ram, and do not do much more than web browsing IM etc at one time, no heavy intesive apps and yet webpages like ESPN and the clubpolk forums (polk audio) for example stutter like hell when I scroll. Its DRIVING ME BANANAS!

Whats the deal with this? Any tips?

This is exactly why I returned mine. It's a no go until they Apple fixes this issue. No reason to by a computer that looks and acts like this.

 

[Ploki]

You certainly have a vivid imagination with a propensity for negative assumptions....

If all I did was surf the web, I sure wouldn't have a maxed out MBP for such a simple task.

you were talking in context to chrome. This laptop should feel no benefits from running 16GB or 8GB with chrome, I currently have 10 tabs in Safari opened, a big-band project in Logic Pro and due to fast SSD still have 10+1GB of ram free.

 

[w00t951]

If you want a website that lags on a cMBP with Chrome and Safari on Windows and Mac OS, then try either Ars Technica or The Verge.

 

[nontroppo]

retina display -> hidpi mode -> safari lags. Conclusion: it's the resolution.

Am I missing some basic inductive logic.

9+million pixels (higher aggregate resolution) == no lag
5million pixels (lower resolution) == lag

"Because it is pushing so many pixels" (which you have now morphed into the more generic "resolution") is not accurate. If you said this is a bug related to properly programming for HiDPI mode, then fine, but you didn't and still aren't. You are saying "resolution" and were saying "pixels"; both of which are inaccurate descriptions of software bugs triggered by a particular API mode new Macs run under.