ASUS P5NSLI: Core 2 Duo and SLI on a Budget
by Gary Key on August 22, 2006 5:30 AM EST- Posted in
- Motherboards
Application Performance
We decided to test a few real world applications that typically stress the CPU, memory, and storage systems to see if the results from our synthetic memory tests carry over to the desktop. Our tasks include three activities that are common on the desktop. Our first test was to measure the time it takes to shrink the entire Office Space DVD that was extracted with AnyDVD into a single 4.5GB DVD image utilizing Nero Recode 2. Our second test utilizes WinRAR 3.6 and measures the time it takes to compress our test folder that contains 444 files, 10 folders, and has 602MB of data.
Our third test consists of utilizing Exact Audio Copy as the front end for our version 3.98a3 of LAME. We setup EAC for variable bit rate encoding, burst mode for extraction, use external program for compression, and to start the external compressor upon extraction (EAC will read the next track while LAME is working on the previous track, thus removing a potential bottleneck with the optical drive). Our test CD is INXS Greatest Hits, a one time '80s glory masterpiece containing 16 tracks totaling 606MB of songs. The results of our tests are presented in minutes/seconds with lower numbers being better.
Unlike the synthetic results where the NVIDIA 570SLI scored well in the Buffered Sandra benchmarks, SuperPI 2M, and Latency tests this chipset scored at the bottom in the DDR2-533 and DDR2-667 tests. However, the board made an amazing comeback at DDR2-800. The other chipsets performance scaled very little from DDR2-533 to DDR2-800 but the NF570SLI scores improved up to 10% in the same range. It is obvious you will want to run this board at DDR2-800 and therein is the critical issue with this board. The memory voltage limits you to 2.1V which will severely hamper your ability to increase the memory clocks on this chipset. This is a chipset that thrives on high memory bandwidth and scales very well up to its limits, but it will be held back due to the memory voltage options as most memory that runs at DDR2-1000 will need 2.2V minimum with 2.3V being the average.
We decided to test a few real world applications that typically stress the CPU, memory, and storage systems to see if the results from our synthetic memory tests carry over to the desktop. Our tasks include three activities that are common on the desktop. Our first test was to measure the time it takes to shrink the entire Office Space DVD that was extracted with AnyDVD into a single 4.5GB DVD image utilizing Nero Recode 2. Our second test utilizes WinRAR 3.6 and measures the time it takes to compress our test folder that contains 444 files, 10 folders, and has 602MB of data.
Our third test consists of utilizing Exact Audio Copy as the front end for our version 3.98a3 of LAME. We setup EAC for variable bit rate encoding, burst mode for extraction, use external program for compression, and to start the external compressor upon extraction (EAC will read the next track while LAME is working on the previous track, thus removing a potential bottleneck with the optical drive). Our test CD is INXS Greatest Hits, a one time '80s glory masterpiece containing 16 tracks totaling 606MB of songs. The results of our tests are presented in minutes/seconds with lower numbers being better.
 |
 |
 |
| Click to enlarge |
Unlike the synthetic results where the NVIDIA 570SLI scored well in the Buffered Sandra benchmarks, SuperPI 2M, and Latency tests this chipset scored at the bottom in the DDR2-533 and DDR2-667 tests. However, the board made an amazing comeback at DDR2-800. The other chipsets performance scaled very little from DDR2-533 to DDR2-800 but the NF570SLI scores improved up to 10% in the same range. It is obvious you will want to run this board at DDR2-800 and therein is the critical issue with this board. The memory voltage limits you to 2.1V which will severely hamper your ability to increase the memory clocks on this chipset. This is a chipset that thrives on high memory bandwidth and scales very well up to its limits, but it will be held back due to the memory voltage options as most memory that runs at DDR2-1000 will need 2.2V minimum with 2.3V being the average.
Facebook
Twitter
RSS
27 Comments
View All Comments
Gary Key - Tuesday, August 22, 2006 - link
That is due to the fact they are using a different chipset than the AM2 family although the marketing language is the same.
scott967 - Tuesday, August 22, 2006 - link
I'm trying to understand the chart on memory which compares different chipsets. The Via PT580 falls apart on Sandra standard going from 533 to 667 memory. Is this correct?scott s.
.
Gary Key - Tuesday, August 22, 2006 - link
That is correct. ASRock and VIA have figured out the issue, just waiting on a fix that hopefully is bios related and nothing else.
Spacecomber - Tuesday, August 22, 2006 - link
This came up before with another article, but perhaps it needs to be said again, I wish that Anandtech would stop using charts showing comparitive FPS that don't show a full FPS axis that starts with zero.I understand that you are trying to highlight the small differences that are being measured and that if you have a chart that uses a proper axis, starting at zero, these differenes are harder to see. However a chart with an axis starting with zero is still a better representation of the results than using a distorted graph to draw out the differences.
Essentially, all you have graphed are the differences between the different results, and if this is what you want to do that is fine. Just relabel the graph and change the axis to show this. Call it something like "Increase in FPS with Memory Speeds Faster than DDR2-663" and then have an axis that runs from 0 to 5 FPS, since that should about cover all your results.
Obviously, such a graph would not be very appealing or interesting, but it would be in better keeping with your data. And, the fact that it doesn't seem to be a very informative graph is precisely my point. Trying to dress these charts up, which really are only charts of the small differences between your results, as if they also provide a relative comparison of the different FPS with different motherboards and different memory timings, simply confounds things. You would do better to pick one or the other to represent, but not mash both together as you are doing now.
It is bad enough that these statistics are posted in such a manner that pays little heed to the kinds of variations that are involved. Magnifying tiny differences in order to make them seen more significant only compounds the problem. Without these distorted graphs a reader might more correctly conclude that the differences in the frame rates, comparing these two different motherboards while using memory running at different speeds, are essentially insignificant. And, drawing out speculative conclusions, based on the perception of any differences, is most likely just much ado about nothing.
hibachirat - Wednesday, August 23, 2006 - link
I don't mind those. But the red and green lines are to close for my red-green color blindness. I can almost tell them apart...but would be nice it the green was brightened and/or the red darkened just a bit.Gary Key - Tuesday, August 22, 2006 - link
Zero based graphs are available by clicking on the orginal image. :)Gary Key - Tuesday, August 22, 2006 - link
Our full review will not utilize these charts. Instead of separating the information and showing pages and pages of the data we felt like this was the best way to collectively show it all at once. We end up with either a graph that has the majority of data points stacked into a single line path or the other evil of not having a zero based graph. We are still working on an updated engine so hopefully this issue disappears quickly or we go back to the bar charts.
Personally, it really bothers me not to have a zero base graph. I will work on another alternative today and update the article if it works. Thanks for the comments and we do agree with you.
JarredWalton - Tuesday, August 22, 2006 - link
We have added a zero-based graphs as pop-ups if you want to see those results. The number tables at the bottom of the charts are intended to help you see that the scores really aren't that far apart, but now you can see the true relative difference.shecknoscopy - Tuesday, August 22, 2006 - link
Well, I've never been that discouraged with their axis labeling, but I could see how someone unfamiliar with the world of statistics could be misled by purported performance differences that are actually within the measurement error.Personally, if I were the one reporting these data, I'd use <b>both</b> methods. Plot the data as you currently do - so as to highlight subtle differences, and <b>also</b> place them on a full graph (where y ranges between 0 and the maximum observed value) in an inset. That way you get a nice zoom-in on the "interesting stuff," and a smaller zoom-out to illustrate that the differences are typically minor, compared to the absolute values.
I'll also point out that, if you <i>really</i> want to get persnippity about their stats reporting, you should demand that they repeat their tests several times, and report each datum with an error bar. :)
Of course, most of my suggestions for improvement involve the word "bar."
-sheq
Renoir - Tuesday, August 22, 2006 - link
I feel it's important to put a lot of these results in perspective with regards to their level of significance. For me personally when looking at results I find the thing that I find most useful is percentages. Lately it seems that a lot of system variables (memory timings/frequency, cpu cache etc) often result in differences of less than 10% in most cases which to me isn't that significant when just getting 1 higher speed bin on your cpu would get you that and probably for less money than say buying the very best ram. I guess I'm saying that when I see graphs that are zoomed in to highlight minor differences I find myself thinking "ok I see why they've done that but it would be nice to be given a percentage so that I can make a quick and dirty evaluation of whether the difference is significant or not". Just some random thoughts :-)