Quote Originally Posted by Mr. K6 View Post
Forgive my noobishness, but is that as easy as getting them from Intel?

Thanks, just did
Get them directly from intel and extract the linpack_xeon32.exe and linpack_xeon64.exe's do you linx folder.

Quote Originally Posted by acebmxer View Post
Link is on the first page of this thread.
The first page is no longer up to date.

Quote Originally Posted by R37ribution View Post
The RTL settings have been known to auto detect too aggressively, you would know this if you browsed i4memory.com. Here is an article on it. There is a formula for RTL and also a link in that thread to an Excel sheet which can be downloaded to guesstimate your RTL. The value you get from the Excel sheet is usually within 1-2. You are correct, each board is different as the traces are longer/shorter going from the processor to the memory but its only going to throw off the RTL by a 1-2 usually and the Excel sheet as a parameter where you can set the latency from processor to RAM (it is defaulted to that of the R3E IIRC).

I apologize about the bad info on the vtt, I don't own a Gulftown. I do know that when my vtt is set to low my gflops are adversely affected on my 3520.
So, you told him to tighten his RTL values because auto detect is too aggressive? Way to change your story buddy.
Initially you said his RTL's were 'way too high' and to drop them to 54/55... Which is it?
Also, he doesn't have an R3E, he has a P6X58D.

Quote Originally Posted by LennyRhys View Post
It's not RTL causing my low GFlops - I've had them set at 58,59,60 for a while now and the GFlop fluctuation persists, but it's definitely more pronounced as I change voltages. I can lose as many as 10 GFlops with one 60mV increment...

After the above run with 58GFlops I re-ran LinX about 10 mins later after leaving my PC powered off. The test was run again with the exact same settings, and voila my GFlops have gone back to 84... but this time I got an error at loop 16. I can tell when GFlops are going to be high because the load temps are much higher, but like I said I didn't change any voltages or memory subtimings... this run is with page file enabled and standard boot, which has given me the best results yet.



As for fine-tuning tRL values - I tried, and it makes no difference. 56,57,58 yield the same results as 58,59,60; and anything below 56 on A doesn't POST.

As for VTT/QPI being too low, LinX still pulls 80+ GFlops below 1.35v, so I guess I just have to find the right ratio as Pilsy said. I've taken QPI all the way to 1.45v only to have diminished returns, so there's still LOTs of tweaking required here in the lower voltage register... I've never found overclocking such a challenge (or so frustrating) in all my life - nothing makes sense!!
RTL and tRL are different values. tRL is NOT exposed to the BIOS on any motherboard EXCEPT the R3E, and even then, it's ONLY with the 0003 beta bios, which is now no longer useful since it's got the smaller intel orom, vs 1502 which you can update the orom.

I suspect you're right and you're running into page file issues. Disable it and try booting into diagnostic mode. With 6GB installed and my page file off, I still can test 5120MB LinX. If LinX memory is paged out to disk... You will have a sharp drop off in GFlops.

I also suspect your core voltage is too low. My cpu will get into windows at 4585mhz with as low as 1.4v, but isn't stable until 1.4875v.
Also, I haven't seen any IOH's that needed more than 1.16v. The IOH doesn't have any impact on memory, so I'm not sure why that would make any difference. I bet you run into dropped memory channels again. Maybe your IMC is drifting enough to cause your hard set RTL's to be too low. You mentioned earlier that your c channel was detected at 61 cycles... but you have it set to 60.

Lastly, to keep every bit of performance, make sure you leave c-states enabled.

Quote Originally Posted by Ace. View Post
very hot zoson
My avatar, or my cpu?