CPU polling with auto, Driver level and low level fan control

[EdKiefer]

This is my first post, hope this is right spot to ask question.

I would like to know how the stock auto fan control is compared to driver level and low level of AB and RT.

Meaning if we set a curve in AB would this be same CPU overhead use if we keep polling rate the same as stock ?.

If using a single speed % with no curve would that use less than even stock auto fan control (not sure how the stock auto relates to CPU for its polling of temps.

[Unwinder]

Originally Posted by EdKiefer

This is my first post, hope this is right spot to ask question.

I would like to know how the stock auto fan control is compared to driver level and low level of AB and RT.

Meaning if we set a curve in AB would this be same CPU overhead use if we keep polling rate the same as stock ?.

If using a single speed % with no curve would that use less than even stock auto fan control (not sure how the stock auto relates to CPU for its polling of temps.

Default fan control and low-level automatic fan control in RT doesn't add any CPU load because fan speed automation is performed by dedicated fan controller chip at hardware level. RT just allows you to adjust hardware fan controller parameters.
Software automatic fan control provided in Afterburner and in RT (in form of fan profiles scheduler) does add some CPU overhead because on each fan speed update iteration (you can adjust fan speed update period in properties) Afterburner will ask the display driver to report GPU temepratures, calculate new target fan speed and ask the display driver to apply it if necessary. It will consume some CPU resources of course.
If you're experienced user then you may edit MSIAfterburner.cfg and change ShowPerformanceProfilerStatus from 0 to 1 to display performance profiler info into MSI Afterburner hardware monitor window. It will show you how many CPU time is eaten by software fan speed automation on each iteration.

[EdKiefer]

Originally Posted by Unwinder

Default fan control and low-level automatic fan control in RT doesn't add any CPU load because fan speed automation is performed by dedicated fan controller chip at hardware level. RT just allows you to adjust hardware fan controller parameters.
Software automatic fan control provided in Afterburner and in RT (in form of fan profiles scheduler) does add some CPU overhead because on each fan speed update iteration (you can adjust fan speed update period in properties) Afterburner will ask the display driver to report GPU temepratures, calculate new target fan speed and ask the display driver to apply it if necessary. It will consume some CPU resources of course.
If you're experienced user then you may edit MSIAfterburner.cfg and change ShowPerformanceProfilerStatus from 0 to 1 to display performance profiler info into MSI Afterburner hardware monitor window. It will show you how many CPU time is eaten by software fan speed automation on each iteration.

Thank you for detail explanation of the polling, that is what I wanted to know, so low level HW does it free as it has its own monitoring.

One last question, you know coolbits has option for "fan always max speed" or something similar as OC fan option, I take it this is not low level as drivers doing it ?.

Thanks for your input, BTW both AB/RT look like great apps .

Edit: I see AB 1.2 adds cpu monitoring now ,I guess this is what you were referring too in last sentence .

""# Added configuration file setting allowing power users to display performance profiler status informaition in the hardware monitor window. The information allows estimating average CPU performance hit caused by hardware monitor and software automatic fan control layers
# Optimized timer message queue processing under high CPU load conditions for better hardware monitoring and software automatic fan control events handling""