Reply to thread

Message: <blockquote data-quote="joz" data-source="post: 519079" data-attributes="member: 70244">I got your points there Micropolis.I was suggesting this because I do not have performance issues but HTPCInfo is kicking my machine up to higher power levels (P-states, Cool & Quiet paramater).I managed to get it to settle on half throttling with RMClock (Multiplier of 9x = 1,8GHz) when idling MP. If I turn HTPCInfo off then it manages to stick with the lowest P-state (5x = 1 GHz). I'll experiment with the options in config, maybe disable the tv/client monitor since you suggest that being the most resource intensive.Currently I have everything turned on and I can see spikes (which is actually quite good for now to test the stability of my undervolt <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />) in the throttling that's done. It gets up to high power for a second (or less) and then returns to either low or mid state. This happens on say a minute cycle. But as I said I'll test with settings and see what I can do to lower it all. This issue occurs on my server/HTPC (which is the tv server also) and is on most of the time so I'd like to keep power usage to a minimum. My clients do not seem bothered by it at all but they are way more powerfull then the server is.-------EDIT------Disabled monitor tv clients and tv server on the machine but that did not really help. Also tried not loading the values on startup and then not go in the plugin and check the p-state, same deal, stuck @ 9x or higher (13) instead of between 5x and 9xI think load will be important for the more energy aware MP users (like me). I will test a little more with these settings to see if I can get it to lower.-------EDIT2------I disabled also sensor monitoring and harddisk monitoring and when I run MP it still gets kicked up to 9x. It then is pretty stable on 9x, doesn't go up to 13x.The weird thing is that I told RMClock to only throttle up when a load on one core reaches 80% of the maximum. However MP in taskmanager only takes up somewhere between 20 and 25 percent. 25% (with HTPCInfo on, little lower if off but isn't that big of a difference) of 1,8 GHz is 0,425 GHz (I know you can't really calculate like that but just for the sake of things for now), which is well below 80% of 1GHz.So not really sure how all it is done but could it maybe be that you have some background workers doing work for you and maybe have set them on high or medium prio? And that's what's causing RMClock to throttle up unnecessarily? Maybe, if possible, a lowest priority for this is best?It's not another process that's causing it, everything else takes up say 1 percent or something. RMClock does throttle down correctly when MP is off and when MP is on without HTPCInfo on.</blockquote>

Verification