The problem with Sandy Bridge was simple: if you wanted to use Intel's integrated graphics, you had to buy a motherboard based on an H-series chipset. Unfortunately, Intel's H-series chipsets don't let you overclock the CPU or memory—only the integrated GPU. If you want to overclock the CPU and/or memory, you need a P-series chipset—which doesn't support Sandy Bridge's on-die GPU. Intel effectively forced overclockers to buy discrete GPUs from AMD or NVIDIA, even if they didn't need the added GPU power.

The situation got more complicated from there. Sandy Bridge's Quick Sync was one of the best features of the platform, however it was only available when you used the CPU's on-die GPU, which once again meant you needed an H-series chipset with no support for overclocking. You could either have Quick Sync or overclocking, but not both (at least initially).

Finally, Intel did very little to actually move chipsets forward with its 6-series Sandy Bridge platform. Native USB 3.0 support was out and won't be included until Ivy Bridge, we got a pair of 6Gbps SATA ports and PCIe 2.0 slots but not much else. I can't help but feel like Intel was purposefully very conservative with its chipset design. Despite all of that, the seemingly conservative chipset design was plagued by the single largest bug Intel has ever faced publicly.

As strong as the Sandy Bridge launch was, the 6-series chipset did little to help it.

Addressing the Problems: Z68

In our Sandy Bridge review I mentioned a chipset that would come out in Q2 that would solve most of Sandy Bridge's platform issues. A quick look at the calendar reveals that it's indeed the second quarter of the year, and a quick look at the photo below reveals the first motherboard to hit our labs based on Intel's new Z68 chipset:

ASUS' P8Z68-V Pro

Architecturally Intel's Z68 chipset is no different than the H67. It supports video output from any Sandy Bridge CPU and has the same number of USB, SATA and PCIe lanes. What the Z68 chipset adds however is full overclocking support for CPU, memory and integrated graphics giving you the choice to do pretty much anything you'd want.

Pricing should be similar to P67 with motherboards selling for a $5—$10 premium. Not all Z68 motherboards will come with video out, those that do may have an additional $5 premium on top of that in order to cover the licensing fees for Lucid's Virtu software that will likely be bundled with most if not all Z68 motherboards that have iGPU out. Lucid's software excluded, any price premium is a little ridiculous here given that the functionality offered by Z68 should've been there from the start. I'm hoping over time Intel will come to its senses but for now, Z68 will still be sold at a slight premium over P67.

Overclocking: It Works

Ian will have more on overclocking in his article on ASUS' first Z68 motherboard, but in short it works as expected. You can use Sandy Bridge's integrated graphics and still overclock your CPU. Of course the Sandy Bridge overclocking limits still apply—if you don't have a CPU that supports Turbo (e.g. Core i3 2100), your chip is entirely clock locked.

Ian found that overclocking behavior on Z68 was pretty similar to P67. You can obviously also overclock the on-die GPU on Z68 boards with video out.

The Quick Sync Problem

Back in February we previewed Lucid's Virtu software, which allows you to have a discrete GPU but still use Sandy Bridge's on-die GPU for Quick Sync, video decoding and basic 2D/3D acceleration.

Virtu works by intercepting the command stream directed at your GPU. Depending on the source of the commands, they are directed at either your discrete GPU (dGPU) or on-die GPU (iGPU).

There are two physical approaches to setting up Virtu. You can either connect your display to the iGPU or dGPU. If you do the former (i-mode), the iGPU handles all display duties and any rendering done on the dGPU has to be copied over to the iGPU's frame buffer before being output to your display. Note that you can run an application in a window that requires the dGPU while running another that uses the iGPU (e.g. Quick Sync).

As you can guess, there is some amount of overhead in the process, which we've measured to varying degrees. When it works well the overhead is typically limited to around 10%, however we've seen situations where a native dGPU setup is over 40% faster.

Lucid Virtu i-mode Performance Comparison (1920 x 1200—Highest Quality Settings)
  Metro 2033 Mafia II World of Warcraft Starcraft 2 DiRT 2
AMD Radeon HD 6970 35.2 fps 61.5 fps 81.3 fps 115.6 fps 137.7 fps
AMD Radeon HD 6970 (Virtu) 24.3 fps 58.7 fps 74.8 fps 116.6 fps 117.9 fps

The dGPU doesn't completely turn off when it's not in use in this situation, however it will be in its lowest possible idle state.

The second approach (d-mode) requires that you connect your display directly to the dGPU. This is the preferred route for the absolute best 3D performance since there's no copying of frame buffers. The downside here is that you will likely have higher idle power as Sandy Bridge's on-die GPU is probably more power efficient under non-3D gaming loads than any high end discrete GPU.

With a display connected to the dGPU and with Virtu running you can still access Quick Sync. CrossFire and SLI are both supported in d-mode only.

As I mentioned before, Lucid determines where to send commands based on the source of the commands. In i-mode all commands go to the iGPU by default, and in d-mode everything goes to the dGPU. The only exceptions are if there are particular application profiles defined within the Virtu software that list exceptions. In i-mode that means a list of games/apps that should run on the dGPU, and in d-mode that is a smaller list of apps that use Quick Sync (as everything else should run on the dGPU).

Virtu works although there are still some random issues when running in i-mode. Your best bet to keep Quick Sync functionality and maintain the best overall 3D performance is to hook your display up to your dGPU and only use Sandy Bridge's GPU for transcoding. Ultimately I'd like to see Intel enable this functionality without the use of 3rd party software utilities.

SSD Caching
Comments Locked


View All Comments

  • dagamer34 - Wednesday, May 11, 2011 - link

    Like most technologies, stay away from first-gen implementations.
  • iwod - Wednesday, May 11, 2011 - link

    I wonder if you could install 32GB DDR3 RAM, and just use 20GB of that as Intel SRT.

    It would be interesting to see how its performance went.
  • kmmatney - Wednesday, May 11, 2011 - link

    Wouldn't be persistent between restarts, so that's a problem right there. It would have to build up the cache every time you reboot, and you couldn't use "Max Cache" mode, so you'd have to wait for the HDD for all writes.
  • liveonc - Wednesday, May 11, 2011 - link

    In this article, it was pointed out that using an SSD is still better for those who want speed. But is a SATA3 SSD & SATA2 Velociraptor combo possible? Or what about an SSD + SSD/HDD combo? Some sort of comprimise w/o the great penalties, or smaller penalties & greater value?
  • dgingeri - Wednesday, May 11, 2011 - link

    I've seen similar numbers using a smaller SSD with Windows 7's ReadyBoost, and it kept the most used data in the cache better. I'd prefer just using that, as it seems more predictable.
  • jordanclock - Wednesday, May 11, 2011 - link

    This IS a big deal. However, a comparison of performance between SRT and ReadyBoost would be handy. Especially ReadyBoost with USB3.
  • dgingeri - Wednesday, May 11, 2011 - link

    you can (and I have) set up ReadyBoost to a SATA SSD. I had a 60GB OCZ Apex as my ReadyBoost drive for about 6 months, before I got my dual Vertex 2s as a new boot drive. Windows 7 has a limit of 32GB for Readyboost usage, though. It made a heck of a difference in boot time and some program load time, however, it took a little while to get the caching set up right to cache what I actually used on a regular basis. It started caching Firefox rather quickly, but took it a while to pick up on caching Diablo 2.
  • randinspace - Wednesday, May 11, 2011 - link

    I still haven't been able to finish the multiplayer mode due to hardware issues stranding me on a glorified netbook.
  • DesktopMan - Wednesday, May 11, 2011 - link


    Shouldn't this work perfectly fine to enable the IGPU when connected to the DGPU without any of the driver nonsense?
  • Hrel - Wednesday, May 11, 2011 - link

    I'd REALLY like to see you guys compare this SRT caching to two of the fastest 7200rpm drives out there in RAID 0. Cause 1-4 seconds on launching applications on loading game levels isn't work 100 extra bucks.

    So compare configurations: 1 MD
    1 MD with Cache
    2MD in RAID 0 (MD = Mechanical Disk)
    2 MD in RAID 0 with cache
    Vertex 3 SSD by itself (and/or the really fast Corsair one)

    You already have most of this testing done and in this article.

    PLEASE PLEASE PLEASE PLEASE do this soon! Thanks guys!

Log in

Don't have an account? Sign up now