We've been running our public performance database tool, Bench, for a few years now. Bench allows you to have direct access to the performance data we use in our reviews, segmented according to product category. Today we have five major product categories in Bench: CPU, GPU, Smartphone, Mobile and SSDs.

CPU Bench is the longest running without significant changes. You can actually compare Intel's most recently released Sandy Bridge E CPU to an old Core 2 Duo E6550 from four years ago in a number of tests using the tool. 

GPU Bench has always posed a more significant challenge. Drivers and test platforms change very frequently, which often precludes us from keeping a running tally of benchmarks similar to what we do on the CPU side. We used our Radeon HD 7970 review as the kicking off point for our brand new PCIe 3.0 testbed for GPUs going forward - a platform we hope to keep in place for at least the next 12 months. While all of this data is already in the 7970 review, if you want to do any head to head comparisons between GPUs you can now do so using our updated GPU Bench 2012 database. The previous version of the database (GPU Bench 2011) is still available.

Similarly, we've finally updated our Smartphone Bench database. Smartphone Bench 2011 features all of the tests and test data we've been using in our most recent smartphone reviews (e.g. Droid RAZR). We opted against calling it Smartphone Bench 2012 because we plan on updating some of the benchmarks in the new year (e.g. you may have seen one of our new battery life tests in our Eee Pad Transformer Prime Follow-up).

We are in the preliminary stages of planning AnandTech's site refresh for 2012, including updates to Bench. If you have any suggestions you'd like to see implemented, please feel free to leave them as comments here. We already have a number of ideas of things we're trying to implement, but your opinions are the most important here so I'm always eager to listen if you're willing to share.

At AMD’s Fusion Developer Summit 2011 AMD announced Graphics Core Next, their next-generation GPU architecture. GCN would be AMD’s Fermi moment, where AMD got serious about GPU computing and finally built an architecture that would serve as both a graphics workhorse and a computing workhorse. With the ever increasing costs of high-end GPU development it’s not enough to merely develop graphics GPUs, GPU developers must expand into GPU computing in order to capture the market share they need to live well into the future.

At the same time, by canceling their 32nm process TSMC has directed a lot of hype about future GPU development onto the 28nm process, where the next generation of GPUs would be developed. In an industry accustomed to rapid change and even more rapid improvement never before have GPU developers and their buyers had to wait a full 2 years for a new fabrication process to come online.

All of this has lead to a perfect storm of anticipation for what has become the Radeon HD 7970: not only is it the first video card based on a 28nm GPU, but it’s the first member of the Southern Islands and by extension the first video card to implement GCN. As a result the Radeon HD 7970 has a tough job to fill, as a gaming card it not only needs to deliver the next-generation performance gamers expect, but as the first GCN part it needs to prove that AMD’s GCN architecture is going to make them a competitor in the GPU computing space. Can the 7970 do all of these things and live up to the anticipation? Let’s find out…

If desktop graphics hardware can be more than a little confusing, deciphering performance of mobile graphics parts can be (and has historically been) an absolute nightmare. Way back in the day it was at least fairly easy to figure out which desktop chip was hiding in which mobile kit, but both AMD and NVIDIA largely severed ties between mobile and desktop branding. They may not want to readily admit that, and in the case of certain models they still pretty heavily rely on the cachet associated with their desktop hardware, but it's by and large true. So to help you make sense of mobile graphics, we present to you the first in what will hopefully be a regular series of guides.

We first met LucidLogix (now just Lucid) 2.5 years ago at IDF. The promise was vendor-agnostic multi-GPU setups with perfect performance scaling. The technology was announced at a very important time. Intel and NVIDIA were battling out support for SLI on Nehalem motherboards. NVIDIA didn't want SLI enabled on any non-NVIDIA chipsets, and Intel wasn't about to let NVIDIA build any chipsets for Nehalem. Lucid's Hydra technology seemed to be exactly what we needed to get around the legal holdup that kept Nehalem users from enjoying SLI.

Three things made Lucid's technology less interesting as time went on. Hydra took two years to come to market, NVIDIA enabled SLI on Intel platforms and single GPU performance got really, really good.

What made Lucid's Hydra tech possible was a software layer that intercepted OpenGL and DirectX calls from the CPU and directed them to a GPU of Lucid's choosing. While Hydra saw limited success, parts of the technology had another application.

Read on for our performance preview of Lucid's Virtu for Sandy Bridge platforms.