Closed Bug 1362613 Opened 7 years ago Closed 6 years ago

Enable high performance power profile

Categories

(Infrastructure & Operations :: RelOps: General, task, P5)

Product:
Infrastructure & Operations
Component:
RelOps: General
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: gps, Assigned: markco)

References

(Blocks 1 open bug)

Details

By default, the Windows power profile is set in some blended mode that doesn't max power/CPU in exchange for saving some power.

As discovered in bug 1323106, this default power mode can make the Firefox build system 60+s slower than "high performance" mode on Xeons.

I think we should set the power profile to "high performance" on as many Windows machines as possible.

In AWS, we should do this no questions asked. Although I'm not sure if it will have an effect because I /think/ that unless you are on the c4.8xlarge instances and have full control of the host, you can't actually control power settings (since there is shared tenancy and power is a global thing). But it certainly can't hurt.

In our data centers, we may want to think about the implications of changing this setting. I'm not sure if it will increase active power draw when idle. But if it does, this could incur thousands of dollars in electricity costs via extra cooling needed for extra generated heat.

Enabling the "high performance" power profile is trivial:

  $ powercfg.exe /SETACTIVE 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

We already do this in puppet/modules/hardware/manifests/highperformance.pp. Although I'm not sure where all that runs. Certainly not on TC workers.
Note explaining the priority level: P5 doesn't mean we've lowered the priority, but the contrary. However, we're aligning these levels to the buildduty quarterly deliverables, where P1-P3 are taken by our daily waterline KTLO operational tasks.
Priority: -- → P5
We won't change this for buildbot. markco has it on his list to look at for new TC hardware.
Assignee: nobody → mcornmesser
Component: Buildduty → RelOps
Product: Release Engineering → Infrastructure & Operations
I am starting to to test this on the moonshot hardware to see what the impact is. 

grenade: has this been addressed with the AWS workers? If not how do you feel about having it was of the items we look at during the work week?
Flags: needinfo?(rthijssen)
testing on beta worker types. if it doesn't break any tests, i'll roll it out to the rest of the worker types.
https://github.com/mozilla-releng/OpenCloudConfig/commit/79cf49c88b01035480f266ff507f75b48e2594d8
Flags: needinfo?(rthijssen)
I think that means we can close this bug!
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.