4 ms·
Running the benchmark in the game settings, I got these results on my wholly-unsuitable-for-any-gaming 2012 Retina MacBook Pro (GeForce GT 650M). Highest Gfx s
by kalleboo 10y ago
Running the benchmark in the game settings, I got these results on my wholly-unsuitable-for-any-gaming 2012 Retina MacBook Pro (GeForce GT 650M).
Highest Gfx settings (default). 2800x1700px window. Best out of 2 runs:
Chrome 56: 33 fps
Safari 10.0.3: 29 fps
Firefox 51: 13 fps
- fb03 10y agoaww, you think your GT650M is unsuitable for gaming? you should try my for-development-only first gen core i7 (920!) with a GEFORCE GTX 275 ;P I can still play Team Fortress 2 at 1080p just fine on this tho ;)
- kalleboo 10y agoPart of the issue is that the laptop has a 3K display (2880x1800) running in scaled mode (3840x2160). And that it has poor cooling and overheats/throttles down at the drop of a hat. And that it's a Mac.
- tgb 10y agoIs the 275 actually slower than a 650M?
- mappu 10y agohttp://www.tomshardware.com/reviews/gpu-hierarchy,4388.html http://www.tomshardware.com/reviews/gpu-hierarchy,4388.html puts the 275 in the same ballpark as the full 650, and the 650M has the same GK107 chip as the 650 but underclocked by 20-30%. So i think my money is on the 275 being faster.
- kasparsklavins 10y agoI have a 710M in my laptop. When I got it a few years ago, I could run most new releases on a 720p display.
- matt4077 10y agomacOS 12.1, NVIDIA GTX960, i7-6700K, 32GB RAM: Chrome 42fps, Safari 38fps. That's somewhat disappointing, both in absolute terms as well as compared to your values. Although maybe it's being throttled at around 40fps which is probably beyond the point of diminishing returns? Edit: Getting 35fps in Firefox, which seems to support the idea that it's being throttled somewhere around that value.
- clarry 10y agoIntel(R) Core(TM) i7-6600U CPU, 1920x1080, Firefox 50: 7 frames per second EDIT: With low settins & AA off, I get 12 fps. Miserable :(
- roschdal 10y agoFirefox has much worse WebGL performance than Chrome. I will create a bugreport to Firefox about this.