Investigations into Socket 939 Athlon 64 Overclocking
by Jarred Walton on October 3, 2005 4:35 PM EST- Posted in
- CPUs
Encoding Performance
For our encoding performance tests, we used AutoGK 1.96 with both the DivX and Xvid codecs. We encoded chapter 9 from The Sum of All Fears without audio to 75% quality. This results in a file size about 1/3 as large as the original (not counting the audio size). As a more common encoding task, we also encode a Budweiser commercial from 30 MB down to 5 MB, including audio encoding. This results in three encoding passes: the compression test, a first pass, and the final pass. We take the total number of frames in the video (900) and divide it by the time taken, reporting the resulting frames per second. In all AutoGK benchmarks, higher scores will be better.
The performance difference between the slowest and fastest setup is around 50% for every encoding task. AutoGK runs a lot more of the computations within the CPU and doesn't depend much on user input. If you were to take a two-hour movie, the difference between 53 minutes and 79 minutes encoding is very noticeable. Using three passes, a two-hour movie would take around 250 minutes compared to 375 minutes - and all of those results are using the slightly faster DivX codec!
Comparing the value RAM and the performance RAM, the largest gap is at 2.7 GHz, and it's once again 5%. Also of interest is that the 10x270 PC2700 part outperformed the 10x280 PC3200 2T part - although dropping to 1T and PC2700 at 2.8 GHz would have improved performance, it seemed less stable than at PC3200 3-4-4-8-2T. Our CPU was definitely hitting its limit above 2.70 GHz.
For our encoding performance tests, we used AutoGK 1.96 with both the DivX and Xvid codecs. We encoded chapter 9 from The Sum of All Fears without audio to 75% quality. This results in a file size about 1/3 as large as the original (not counting the audio size). As a more common encoding task, we also encode a Budweiser commercial from 30 MB down to 5 MB, including audio encoding. This results in three encoding passes: the compression test, a first pass, and the final pass. We take the total number of frames in the video (900) and divide it by the time taken, reporting the resulting frames per second. In all AutoGK benchmarks, higher scores will be better.
The performance difference between the slowest and fastest setup is around 50% for every encoding task. AutoGK runs a lot more of the computations within the CPU and doesn't depend much on user input. If you were to take a two-hour movie, the difference between 53 minutes and 79 minutes encoding is very noticeable. Using three passes, a two-hour movie would take around 250 minutes compared to 375 minutes - and all of those results are using the slightly faster DivX codec!
Comparing the value RAM and the performance RAM, the largest gap is at 2.7 GHz, and it's once again 5%. Also of interest is that the 10x270 PC2700 part outperformed the 10x280 PC3200 2T part - although dropping to 1T and PC2700 at 2.8 GHz would have improved performance, it seemed less stable than at PC3200 3-4-4-8-2T. Our CPU was definitely hitting its limit above 2.70 GHz.
101 Comments
View All Comments
intellon - Tuesday, October 4, 2005 - link
I understand how/why the memory quality is not too imoprtant (5-9% increase for 100 bucks = not worthy)What I AM unclear about is the cpu itself. Would all the cpu's based on venice hit a same ceiling. Or would a 3800+ reach a higher, more stable, cooler overclock than the 3200+? There is one line that mentions these two cpu's on the first page but no comment on how they would perform when overclocked. Does a 12x help over 9x? Also am I wrong in assuming that you picked 3200+ over 3000+ because of a higher multiplier?
And like people are asking... how bad/good are the other chips? How'll a San Diego 3500+ fare against a Venice 3500+? They're faster as stock, but can they match or exceed overclock performance of venice?
Questions questions questions...
The article was wicked though. I was skeptical about buying a cheaper RAM... but seeing how another $50 is not going to help, I'll save that money for something else.
gplracer - Tuesday, October 4, 2005 - link
Very nice article. It appears to be well thought out. Thanks for the time you spent on it. I would also be nice to have an article of this type with some of the more popular power supplies.I to have had several chips that would overclock such as:
P166 @ 200mhz lol
Celeron 300a @ 450mhz
Duron 600 @ 950mhz
Athlon 1700+ (DLTC3) @ 2374mhz
2600+ at 250x10= 2500mhz
There is no way you could add all of the cpus to the review. I look forward to overclocking a dual core athlon64.
PaBlooD - Tuesday, October 4, 2005 - link
Great Articule.. thanks for that great work.I actually have a A64 3200+ Winchester core with an Epox 9NDA3+ + 512 x2 ocz premier (crap ) and i only can get the procesor to 2150 mhz... i tried with safe memo times.. but nothing..are that bad overclockers the Winchester cores? :S
(excuse my poor english ^_^)
RaulAssis - Wednesday, December 21, 2005 - link
Didi you try memory deviders like 5/6 ?yacoub - Tuesday, October 4, 2005 - link
I definitely appreciate all the walk-through of overclocking an A64 system. Very good article. One thing though - the last few pages with the test result charts... the charts make it look like the entire notion of overclocking is rather pointless since all four colored lines are nearly identical in all but a couple tests. You might want to consider a different type of chart next time that gives a -visual- impression of the benefit to better support the written descriptive increases in performance. Maybe some sort of bar chart would have worked better.JarredWalton - Tuesday, October 4, 2005 - link
I felt the visual impression conveyed exactly what I saw: the difference between the 3000+ and 3200+ in overclocking combined with value and performance RAM is, at best, small. I understand what you're saying, and trust me: I played around with the Excel graphs for many hours. None of the graphs really gave a clear picture, unfortunately. Getting four setups with about 9 settings each into a single chart is messy. Having 80 charts is even worse. Heheh.If someone can show me a preferred chart style, I'll be happy to change the graph for the next installment. The AnandTech graphing engine really wasn't capable of dealing with this type of data set, unfortunately... but Excel was only marginally better.
intellon - Tuesday, October 4, 2005 - link
I guess you could "ZOOM IN" onto the y-axis. For instance: on the last graph HL2 1024x768 4xAA, since the minimum was above 80 and max was below 140, you could set the min and max ranges of y-axis accordingly. or go GNU plot way for a sharper graph.JarredWalton - Tuesday, October 4, 2005 - link
Like the 3DMark GPU scores? I really dislike graphs that don't start at 0, because it hides the reality. (That's why I put the extra paragraph on the 3DMark scores noting specifically that they don't start at 0.) I can blow up a graph so that everyone can see the 1 or 2% margin of victory, but what does that really say? Margin of error on several benchmarks is at least 1 or 2%, and in actual use I don't think anyone will really notice even a 5% difference - I know I don't.Some people will be annoyed by this, but too many people worry about the last 1% of performance. Not because they can notice a difference, but because they want meaningless bragging rights. Sitting in the top positions in an online game requires skill. Getting 1% higher FPS usually just involves throwing more money at your PC than the next guy. Some people like to do that - sort of like some people like muscle cars. I want a fast computer, but I'm not going to lose sleep because my PC is marginally slower than my friend's, you know?
Anyway, I may look into a separate graphing tool. Excel looks fine internally, but getting the graphs into image form didn't work perfectly. The text alignment got a little tweaked when I cut and pasted the data into Photoshop.
Regards,
Jarred Walton
RupertS - Wednesday, October 19, 2005 - link
Be careful, I think Muscle Car owners are a protected class.probedb - Tuesday, October 4, 2005 - link
I'd just like to say cheers for this. It's made me finally get round to trying to OC my system. I purposely bought a 3000+ and Crucial Ballistix for this but have never got round to trying it.I shall give it a go this weekend!!!