Initial 3DMark Notebook Results

While we don’t normally run 3DMark for our CPU and GPU reviews, we do like to run the tests for our system and notebook reviews. The reason is simple: we don’t usually have long-term access to these systems, so in six months or a year when we update benchmarks we don’t have the option to go back and retest a bunch of hardware to provide current results. That’s not the case on desktop CPUs and GPUs, which explains the seeming discrepancy. 3DMark has been and will always be a synthetic graphics benchmark, which means the results are not representative of true gaming performance; instead, the results are a ballpark estimate of gaming potential, and as such they will correlate well with some titles and not so well with others. This is the reason we benchmark multiple games—not to mention mixing up our gaming suite means that driver teams have to do work for the games people actually play and not just the benchmarks.

The short story here (TL;DR) is that just as Batman: Arkham City, Elder Scrolls: Skyrim, and Far Cry 3 have differing requirements and performance characteristics, 3DMark results can’t tell you exactly how every game will run—the only thing that will tell you how game X truly scales across various platforms is of course to specifically benchmark game X. I’m also more than a little curious to see how performance will change over the coming months as 3DMark and the various GPU drivers are updated, so with version 1.00 and current drivers in hand I ran the benchmarks on a selection of laptops along with my own gaming desktop.

I tried to include the last two generations of hardware, with a variety of AMD, Intel, and NVIDIA hardware. Unfortunately, there's only so much I can do in a single day, and right now I don't have any high-end mobile NVIDIA GPUs available. Here’s the short rundown of what I tested:

System Details for Initial 3DMark Results
System CPU (Clocks) GPU
(Core/RAM Clocks)
RAM (Timings)
Gaming Desktop Intel Core i7-965X
4x3.64GHz (no Turbo)
HD 7950 3GB
900/5000MHz
6x2GB DDR2-800
675MHz@9-9-9-24-2T
Alienware M17x R4 Intel Core i7-3720QM
4x2.6-3.6GHz
HD 7970M 2GB
850/4800MHz
2GB+4GB DDR3-1600
800MHz@11-11-11-28-1T
AMD Llano AMD A8-3500M
4x1.5-2.4GHz
HD 6620G
444MHz
2x2GB DDR3-1333
673MHz@9-9-9-24
AMD Trinity AMD A10-4600M
4x2.3-3.2GHz
HD 7660G
686MHz
2x2GB DDR3-1600
800MHz@11-11-12-28
ASUS N56V Intel Core i7-3720QM
4x2.6-3.6GHz
GT 630M 2GB
800/1800MHz

HD 4000@1.25GHz
2x4GB DDR3-1600
800MHz@11-11-11-28-1T
ASUS UX51VZ Intel Core i7-3612QM
4x2.1-3.1GHz
GT 650M 2GB
745-835/4000MHz
2x4GB DDR3-1600
800MHz@11-11-11-28-1T
Dell E6430s Intel Core i5-3360M
2x2.8-3.5GHz
HD 4000@1.2GHz 2GB+4GB DDR3-1600
800MHz@11-11-11-28-1T
Dell XPS 12 Intel Core i7-3517U
2x1.9-3.0GHz
HD 4000@1.15GHz 2x4GB DDR3-1333
667MHz@9-9-9-24-1T
MSI GX60 AMD A10-4600M
4x2.3-3.2GHz
HD 7970M 2GB
850/4800MHz
2x4GB DDR3-1600
800MHz@11-11-12-28
Samsung NP355V4C AMD A10-4600M
4x2.3-3.2GHz
HD 7670M 1GB
600/1800MHz

HD 7660G 686MHz
(Dual Graphics)
2GB+4GB DDR3-1600
800MHz@11-11-11-28
Sony VAIO C Intel Core i5-2410M
2x2.3-2.9GHz
HD 3000@1.2GHz 2x2GB DDR3-1333
666MHz@9-9-9-24-1T

Just a quick note on the above laptops is that I did run several overlapping results (e.g. HD 4000 with dual-core, quad-core, and ULV; A10-4600M with several dGPU options), but I’ve taken the best result on items like the quad-core HD 4000 and Trinity iGPU. The Samsung laptop also deserves special mention as it supports AMD Dual Graphics with HD 7660G and 7670M; my last encounter with Dual Graphics was on the Llano prototype, and things didn’t go so well. 3DMark is so new that I wouldn’t expect optimal performance, but I figured I’d give it a shot. Obviously, some of the laptops in the above list haven’t received a complete review, and in most cases those reviews are in progress.

And with that out of the way, here are the results. I’ll start with the Ice Storm tests, followed by Cloud Gate and then Fire Strike.

3DMark Ice Storm

3DMark Ice Storm

3DMark Ice Storm

3DMark Cloud Gate

3DMark Cloud Gate

3DMark Cloud Gate

3DMark Fire Strike

3DMark Fire Strike

3DMark Fire Strike

As expected, the desktop typically outpaces everything else, but the margins are a bit closer than what I experience in terms of actual gaming. Generally speaking, even with an older Bloomfield CPU, the desktop HD 7950 is around 30-60% faster than the mobile HD 7970M. Thanks to Ivy Bridge, the CPU side of the equation is actually pretty close, so the overall scores don’t always reflect the difference but the graphics tests do. The physics tests even have a few instances of mobile CPUs besting Bloomfield, which is pretty accurate—with the latest process technology, Ivy Bridge can certainly keep up with my i7-965X.

Moving to the mobile comparisons, at the high end we have two laptops with HD 7970M, one with Ivy Bridge and one with Trinity. I made a video a while back showing the difference between the two systems running just one game (Batman), and 3DMark again shows that with HD 7970M, Trinity APUs are a bottleneck in many instances. Cloud Gate has the Trinity setup get closer to the IVB system, and on the Graphics score the MSI GX60 actually came out just ahead in the Fire Strike test, but in the Physics and Overall scores it’s never all that close. Physics in particular shows very disappointing results for the AMD APUs, which is why even Sandy Bridge with HD 3000 is able to match Llano in the Ice Storm benchmark (though not in the Graphics result).

A look at the ASUS UX51VZ also provides some interesting food for thought: thanks to the much faster CPU, even a moderate GPU like the GT 650M can surpass the 3DMark results of the MSI GX60 in two of the overall scores. That’s probably a bit much, but there are titles (Skyrim for instance) where CPU performance is very important, and in those cases the 3DMark rankings of the UX51VZ and the GX60 are likely to match up; in most demanding games (or games at higher resolutions/settings), however, you can expect the GX60 to deliver a superior gaming experience that more closely resembles the Fire Strike results.

The Samsung Series 3 with Dual Graphics is another interesting story. In many of the individual tests, the second GPU goes almost wholly unused—note that I’d expect updated drivers to improve the situation, if/when they become available. The odd man out is the Cloud Gate Graphics test, which scales almost perfectly with Dual Graphics. Given how fraught CrossFire can be even on a desktop system, the fact that Dual Graphics works at all with asymmetrical hardware is almost surprising. Unfortunately, with Trinity generally being underpowered on the CPU side and with the added overhead of Dual Graphics (aka Asymmetrical CrossFire), there are many instances where you’re better off running with just the 7670M and leaving the 7660G idle. I’m still working on a full review of the Samsung, but while Dual Graphics is now at least better than what I experienced with the Llano prototype, it’s not perfect by any means.

Wrapping things up, we have the HD 4000 in three flavors: i7-3720QM, i5-3360M, and i7-3517U. While in theory they iGPU is clocked similarly, as I showed back in June, on a ULV platform the 17W TDP is often too little to allow the HD 4000 to reach its full potential. Under a full load, it looks like HD 4000 in a ULV processor can consume roughly 10-12W, but the CPU side can also use up to 15W. Run a taxing game where both the CPU and iGPU are needed and something has to give; that something is usually iGPU clocks, but the CPU tends to throttle as well. Interestingly, 3DMark only really seems to show this limitation with the Ice Storm tests; the other two benchmarks give the dual-core i5-3360M and i7-3517U very close results. In actual games, however, I don’t expect that to be the case very often (meaning, Ice Storm is likely the best representation of how HD 4000 scales across various CPU and TDP configurations).

HD 4000 also tends to place quite well with respect to Trinity and some of the discrete GPUs, but in practice that’s rarely the case. GT 630M for instance was typically 50% to 100% (or slightly more) faster than HD 4000 in the ASUS N56V Ivy Bridge prototype, but looking at the 3DMark results it almost looks like a tie. Don’t believe those relative scores for an instant; they’re simply not representative of real gaming experiences. And that is one of the reasons why we continue to look at 3DMark as merely a rough estimate of performance potential; it often gives reasonable rankings, but unfortunately there are times (optimizations by drivers perhaps) where it clearly doesn’t tell the whole story. I’m almost curious to see what sort of results HD 4000 gets with some older Intel drivers, as my gut is telling me there may be some serious tuning going on in the latest build.

3DMark for Windows Overview Initial Thoughts on 3DMark “2013”
POST A COMMENT

69 Comments

View All Comments

  • Landspeeder - Tuesday, February 05, 2013 - link

    Drawing a blank mate - ORB? Reply
  • Ryan Smith - Tuesday, February 05, 2013 - link

    Futuremark's Online Results Database. Reply
  • Landspeeder - Tuesday, February 05, 2013 - link

    perfect - thanks Gents. Reply
  • carage - Tuesday, February 05, 2013 - link

    Have you considered notebooks with the possibility of external video upgrades?
    I have a ThinkPad W520 connected to a ViDock via Express Card which houses a GTX 670 4GB.
    The scores I got so far:
    ICE STORM: 97109
    (Beats the Alienware with 7970M)
    CLOUD GATE: 15874
    (Slightly slower than 7970M)
    FIRE STRIKE: 5351
    (Even beats the gaming desktop 7950)
    Reply
  • Notmyusualid - Tuesday, February 05, 2013 - link

    M18x R2.

    i7 3920XM, 16GB CAS10 RAM, ONE 7970M. (Cross-fire equipped, but it locked my system solid the moment the DX11 tests began).

    Left number is my Inspiron 17R SE's result, right is the UX51VZ:

    Ice Storm:
    146723
    273526
    55947

    Cloud Gate:
    18157
    32362
    7159

    Fire Strike:
    4467
    4807
    10467

    It was kind of fun to watch the tests, but a bore after a 3rd time, due to Crossfire issues. Would be nice to run ONE test, but I guess they need to make money, eh?

    Will update when Crossfire works...
    Reply
  • Notmyusualid - Tuesday, February 05, 2013 - link

    Opps, ignore the cut & paste error there from the other poster. I have no 17R, nor UX51VZ.

    Its late in Asia....
    Reply
  • JarredWalton - Tuesday, February 05, 2013 - link

    Interesting... looks like even with the 3920XM you're still getting slower results on Fire Strike than the M17x R4. What drivers are you running? Reply
  • Notmyusualid - Wednesday, February 06, 2013 - link

    RE: I don't see how you saw my results as slower, so here are the comparisons, side-by-side, with data from your graphs, for all, including the Fire Strike tests.

    M18x R2.

    i7 3920XM, 16GB CAS10 RAM, ONE 7970M. (Cross-fire equipped, but it locked my system solid the moment the DX11 tests began).

    Left number is your M17x R4's results, right is the my M18x R2 on ONE 7970M card:

    Ice Storm:
    85072 / 146723 #
    116561 /273526 #
    43727 / 55947 #

    Cloud Gate:
    16729 / 18157 #
    30624 / 32362 *
    6491 / 7159 #

    Fire Strike:
    4332 / 4467 *
    4696 / 4807 *
    8910 / 10467 #

    So to me, I have the M17x system beat in all respects.
    # = My system besting everything on your graphs.
    * = Your HD7950 showing significant gain(s), over the laptops.

    Operating System is Win 8 (Bloatware) x64.
    Graphics drivers are AMD_Catalyst_13.2_Beta3. (13.1 didn't install at all). No CAP file for this one yet I don't think.

    Now to try the Crossfire again...
    Reply
  • jtd871 - Tuesday, February 05, 2013 - link

    Jarred,

    Moar data for you...

    i7-3630QM 3.3GHz
    GT675M 4GB, 9.18.13.623 (306.97 Driver Package)
    8GB 1600 RAM
    Win 7 Pro
    Samsung 830 SSD (if that matters)

    3DMark Basic
    Screen Resolution (if that matters) 1920x1080

    Scenario: Score / Graphics / Physics / Combined
    Ice Storm: 80831 / 109914 / 41967
    Cloud Gate: 12475 / 18162 / 5952
    Fire Storm: 2091 / 2220 / 8146 / 816
    Reply
  • MrSpadge - Tuesday, February 05, 2013 - link

    Wow, seems like FM put some real effort into this one. It's more than "just another 3DMark" :)

    And regarding the currently missing diagnosis information: I think they should partner with some hardware diagnostic tool vendor, like the Argus Monitor team. Whatever FM needs to implement, they already did it. Fair deal: FM integrates their diagnostic in exchange for advertising that they do so.

    There's also more potential in the enhanced result analysis and the nice graphs. And interesting point would be the time between frames. Give a mean and standard deviation and we could judge which system is smoother. Give us a graph and we could easily identify micro stutter.
    Reply

Log in

Don't have an account? Sign up now