What makes 'AVX Offset' not working?

[ffffwh]

Under Linux (or Windows?)
- On non-AVX load [1], max CPU ratio is the ratio I set.
- On AVX load, max CPU ratio is (the ratio - AVXOffset) [2]

Under macOS + Clover
- Max ratio is always (ratio - AVXOffset)

Does 'AVX offset' require OS support, or only BIOS support is sufficient?

If it is the latter case, does it mean Clover does a mistake at calculating the max ratio/freq?

-------------

[1] Prime 95 small FFT with 'CpuSupportsAVX=0'
[2] AVX makes more heat that normal instructions and is used for limited cases (e.g. video software encoding). IMHO it is a good idea to set a higher freq for normal cases, and use AVX Offset to reduce freq in AVX use cases.

 

[e-troc]

Interested in this as well. Just read about it for the first time here:

https://www.tonymacx86.com/threads/8700k-asus-z370-o-c-fail.255983/page-4#post-1780333

Maybe @pastrychef knows more?

 

[pastrychef]

Interested in this as well. Just read about it for the first time here:

https://www.tonymacx86.com/threads/8700k-asus-z370-o-c-fail.255983/page-4#post-1780333

Maybe @pastrychef knows more?

I have no idea why it doesn't work. I just set my offset to 0 in BIOS and forget about it...

 

[e-troc]

I have no idea why it doesn't work. I just set my offset to 0 in BIOS and forget about it...

Have been doing the same since reading your other post. I feel like this should be a sticky or something, pretty much all overclocking guides include setting AVX offset to 1-3, giving unexpected results when using macOS.

 

[pastrychef]

Have been doing the same since reading your other post. I feel like this should be a sticky or something, pretty much all overclocking guides include setting AVX offset to 1-3, giving unexpected results when using macOS.

Not really unexpected... With macOS, if you set an AVX offset, the CPU will always run at the offset speed.

For example, if you have your CPU clocked at 5.1GHz with an AVX offset of 3, in macOS, the CPU will only run at a max Turbo speed of 4.8GHz.

 

[e-troc]

@pastrychef, what I mean is, if you do not know about this behaviour and follow common overclocking guides, you will get unexpected results (non-AVX also running at lower clock).

 

[jiffyslot]

@pastrychef, what I mean is, if you do not know about this behaviour and follow common overclocking guides, you will get unexpected results (non-AVX also running at lower clock).

Gah! I didn't know that about non-AVX!