Overclocking Extravaganza: Radeon HD 4890 To The Max

Combined Memory and Core Overclocking: The Sweet Spot

In this round of tests, we combine our previous maximum overclocks. This is our compromise, in that we show the maximum potential of combined core and memory overclocking rather than effects of memory overclocking over each core clock speed we tested. While the latter option would be more complete, our tests do enough to show people what they need to know to find the sweet spot.

We theorized that with an extreme core clock speed that memory may have become a bottleneck to performance at some point. Despite the fact that increasing memory clock without increasing core clock didn't do much at all, we could see increased benefit beyond what one might expect based on our initial memory overclocking results.

Before we looked at varied memory clock with a stock core clock and varied core clock with a stock memory clock. Let's revisit both of those but also add in a twist. We will also look at percent increase in performance when overclocking memory with a 1GHz core clock and the percent increase in performance when overclocking the core with a 1.2GHz memory clock.

1680x1050    1920x1200    2560x1600

1680x1050    1920x1200    2560x1600

1680x1050    1920x1200    2560x1600

1680x1050    1920x1200    2560x1600

Note that in both cases we see a much bigger boost in performance. This means that while applications tend to be very heavily compute limited, at higher core clock speeds on AMD hardware memory bandwidth increasinly becomes a bottleneck. Now let's take a look at what we get when going from a completely stock part to a maximally overclocked part at 1GHz/1.2GHz (core/mem).

1680x1050    1920x1200    2560x1600

To get a basic idea of what's going on, here's an example of two programs. Remember that this isn't really real world and is just to illustrate the concept.

The first application is completely compute bound and the second is 50% compute bound and 50% memory bandwidth bound. Both tests generate 100 frames per second on a stock Radeon HD 4890. If we increase core clock speed 10%, the first application will generate 110 frames per second, while the second one would only generate 105. This is because we only see the 10% benefit while doing half of the work. If we look at only boosting memory performance 10%, the first program delivers only 100 fps while the second hits 105 again. Pushing both memory and core clock speed up 10% each gives us 110 frames per second from both applications. Basically.

Nothing is really that contrived or works like that, but the important thing to remember is that different applications can make varying use of different resources, and balancing those resources is important to ensuring the best performance in the most efficient package.

So, to find the sweet spot for your overclock, you will want to increase core clock speed as much as you can. Then bump up memory clock and see how high you can get it and remain stable. Use a real world application to test performance at each point and then use a binary search like algorithm to find the sweet spot in a short number of tests. And there you have it. We didn't do this for you, but what's better practice than a little hands on experience right? Besides, if gives readers the opportunity to compare notes in the comments on what the optimal memory clock for a 1GHz core clock on the 4890 would be. Have fun!