www.BlackViper.com: CUV4X-D Memory Tweaking Benchmarks Page 2

> Home > Articles > Mother Boards > CUV4X-D Tweaking Page 2

Testing Breakdown

Test numbers 1 and 2:

Summary Popup

Test 1 started out as a "default" baseline measurement. I have not changed anything from default. 3012, although not to shabby, needed to be raised a bit for giggles...

Test 2 is JUST changing the SDRAM timings to the fastest settings. This tweak alone was THE single most effective thing anyone could do. Take note: Fast Memory = Fast computer! :)

Test number 3:

Summary Popup

This ended up being the WORST setting...by going from "default" to "0.0" DRAM read Latch Delay, this configuration beat out all the others for being the slowest...

Test numbers 4 through 7:

Summary Popup

These are the slower SDRAM timings to see just what the other settings actually would effect in the results. All settings changed VERY minimally...not even really worth the bother...but one point is one point! Just goes to show that going from "64 MB" to "256 MB" Graphics Aperture Size did not do all that much. An interesting thing happened, though, with test 6, (Byte Merge) After applying this setting and rebooting, my network drives would not connect upon boot. They were still there, but not upon logging in...very strange.

Test number 8 and 9:

Summary Popup

In the background, I ran "Task Manager" during test 8 to get a screen shot (Figure 1) of the CPUutilization after the test was complete. In this shot, it looks as though both CPU's are used during the benchmark testing...but as you soon will see, that is not actually true. Hard to believe? Read on...

Test number 9 was just to compile all the previous settings that made a POSITIVE difference in the results, and put them into one. This made the FASTEST settings during test 9.

Task Manager
Figure 1

Test numbers 10 and 11:

Summary Popup

These tests gave me the knowledge that either 1) nVidia cards "work" with the "USWC" setting, or 2) that it makes no difference whether it is enabled or not. I really cannot find any information on it... so I guess that STILL will remain a mystery.

Test 11 was the result of increasing the DRAM Read Latch Delay to "1.5." Funny, the ASUS default settings really WERE the "optimal" ones on this account... :)

Test number 12 and 13:

Summary Popup

I then, before moving along with test 12, installed the latest (as of now) Direct x 8.0a. I was not really surprised to see that it did not gain any performance with this, but actually, decreased just slightly. Go figure.

In the background, I ran "Task Manager" during test 13 to get a screen shot (Figure 2) of the CPU utilization after the test was complete. Remember when I asked if it was using both CPU's for the test? The results are practically identical to test 8 (taking into account the installation of DirectX 8.0a). This just goes to show that the 3dMark2001 does NOT use dual CPU's in the benchmark.This is kind of a shame when you think about it. I think that ALL programs should be multithreaded to some degree.

Task Manager
Figure 2

Articles Index ~ Page 1 - Introduction ~ Page 3 - Summary


Quick Links

In this article:

Introduction
Testing Breakdown
Summary Table
Conclusion

Outside of BlkViper.com:

Sound Blaster Live!
Microsoft / Direct X
VIA Home Page / VIA Chipset Drivers
Mad Onion / 3dMark2001

"Have you tweaked your OS lately?"

Choose the look:
Black or White

 

Original content created: July 28, 2001
All content Copyright © 1999-2008 by Charles "Black Viper" Sparks. All Rights Reserved.
Feedback or Corrections: Contact BV
Copyright Information | Disclaimer | Privacy Policy | Browser Compatibility List | Site Map