How to set up GTL Ref Values for 45nm & 65nm

[davidk21770]

I noticed a similar variation when searching for the correct GTLs. It didn't occur to me to try to use it for tuning!
So, you're suggesting that for a specific set of voltages, the GTLs that give me that max GFLOPs/min Times in LinPak (over several trials -- I usually run 15 before switching to prime95) is the sweet spot? That I should tune for that? See if it's stable and if not, move on?

[carepolice]

Now that you mentioned this sweetspot and GTL's doing changes on Gflops here some old pics that i have stored.


and now today whit 0.635x GTL's

[mikeyakame]

I noticed a similar variation when searching for the correct GTLs. It didn't occur to me to try to use it for tuning!
So, you're suggesting that for a specific set of voltages, the GTLs that give me that max GFLOPs/min Times in LinPak (over several trials -- I usually run 15 before switching to prime95) is the sweet spot? That I should tune for that? See if it's stable and if not, move on?

yeah you should be able to just make sure you use the same problem size for all tests. you can use two different ones, ie like I do, small problem and large problem, just as long as the config is consistent for all the testing runs.

That's how I've always tuned GTL for unknown FSBs heh I just figured others realized the same! I guess it's not as obvious as it looks to me!

Gives me a good idea, and usually if you get it right in Linpack..Prime95 should pass with flying colours provided you haven't hit an FSB Wall on the chip! Usually Linpack picks up the Wall before Prime anyway...nothing says wall more than a hard system lock that can't be tuned around!

[Big Lar]

yeah you should be able to just make sure you use the same problem size for all tests. you can use two different ones, ie like I do, small problem and large problem, just as long as the config is consistent for all the testing runs.

That's how I've always tuned GTL for unknown FSBs heh I just figured others realized the same! I guess it's not as obvious as it looks to me!

Gives me a good idea, and usually if you get it right in Linpack..Prime95 should pass with flying colours provided you haven't hit an FSB Wall on the chip! Usually Linpack picks up the Wall before Prime anyway...nothing says wall more than a hard system lock that can't be tuned around!

I never thought of doing this! Thank you for that. Have not adjusted my Cpu GTL's this way but I just adjusted my NB GTL from .650 to .655 and shaved my time off about .19 and Gflops went up .21.Nice

Larry

[CryptiK]

I have noticed the variation in work throughput and noticed when I had the GTL Refs spot on that the Gflops were very similar within a run, but by the time I noticed I had my system tuned almost perfectly. It's probably a good idea to use this in addition to other methods to get the GTL Refs tuned for the particular FSB.

yeah you should be able to just make sure you use the same problem size for all tests. you can use two different ones, ie like I do, small problem and large problem, just as long as the config is consistent for all the testing runs.

That's how I've always tuned GTL for unknown FSBs heh I just figured others realized the same! I guess it's not as obvious as it looks to me!

Gives me a good idea, and usually if you get it right in Linpack..Prime95 should pass with flying colours provided you haven't hit an FSB Wall on the chip! Usually Linpack picks up the Wall before Prime anyway...nothing says wall more than a hard system lock that can't be tuned around!