Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Power plan capture may be misleading. #148

Open
gambit9009 opened this issue Mar 17, 2022 · 0 comments
Open

Power plan capture may be misleading. #148

gambit9009 opened this issue Mar 17, 2022 · 0 comments
Assignees
Labels
enhancement wave 2 consider this issue for next wave of fixes

Comments

@gambit9009
Copy link
Contributor

gambit9009 commented Mar 17, 2022

The perfstatsanalysis script creates an sp called "proc_PowerPlan".

if not exists (select * from tbl_PowerPlan where ActivePlanName like '%High Performance%')

So if the power plan name is not fully spelled out like that, it may flag "Power Plan is not set to high performance". But, at least in later Windows, you can rename your power plan. PC manufactures may have their own names for plans, etc. Someone could use the High Perf plan and change settings to it, without renaming it. The actual settings under the power plan, like CPU throttling, are really what we are concerned with, and not the name of the plan.

  1. I'm adding this as an issue to PSSDiag to see if we can do better than just capturing the name of the plan.

See also microsoft/SqlNexus#145

@gambit9009 gambit9009 changed the title power plan Power plan capture may be misleading. Mar 17, 2022
@gambit9009 gambit9009 self-assigned this Mar 17, 2022
@PiJoCoder PiJoCoder added the wave 2 consider this issue for next wave of fixes label Apr 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement wave 2 consider this issue for next wave of fixes
Projects
None yet
Development

No branches or pull requests

2 participants