![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
izardFor the applications I usually work with first thing we do is disable all power management. It only brings uncertainty to execution timings which embedded and a lot of telco/enterprise workloads want to avoid.
But for most of performance conscious programmers power management brings a lot of fun. Before recently, there were several states with well documented transitions and timings. Now they are more complex - there are C-states, S-states, P-states and D-states and they interact :) Oh, yes, frequency can also change - both down and up! (HT would bring some more complexity)
Good thing is Intel Vtune XE has a special collection mode to catch some of the transitions I've mention above.
But for most of performance conscious programmers power management brings a lot of fun. Before recently, there were several states with well documented transitions and timings. Now they are more complex - there are C-states, S-states, P-states and D-states and they interact :) Oh, yes, frequency can also change - both down and up! (HT would bring some more complexity)
Good thing is Intel Vtune XE has a special collection mode to catch some of the transitions I've mention above.
