From Fedora Project Wiki
(dptfxtract is non-free, so not essential part of the proposal)
Line 129: Line 129:


<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism: Don't ship both packages by default <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: Don't ship package by default <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->



Revision as of 09:54, 31 July 2019


Better Thermal Management for the Workstation

Summary

Better thermal management and peak performance on Intel CPUs by including thermald in the default install.

Owner

  • Product: Workstation
  • Responsible WG: Workstation


Current status

  • Targeted release: Fedora 31
  • Last updated: 2019-07-31
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Modern Intel-based systems provide sensors and methods to monitor and control temperature of its CPUs. The Thermal daemon will use those sensors to monitor the temperature and use the best available method to keep the CPU in the right temperature envelop. On certain systems this is needed to reach the maximal performance. For optimal performance a per-model thermald configuration should be created, this can either be done by using dptfxtract (available from rpmfusion) or we could ship static configuration files for a set of known models.

For a more details explanation please consult Intel's introduction to thermald.

Benefit to Fedora

Better out-of-the-box experience due to improved cooling methods and performance on Intel systems.

Scope

  • Proposal owners:
- Include the thermald package in the default Workstation install
- Optionally provide patches for thermald to be able to read hardware specific configuration data
- Optionally collect hardware specific configuration data and ship it
  • Other developers: N/A (not a System Wide Change)
  • Release engineering:
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

Install the packages and use e.g. turbostat to monitor the performance. Improvements may only be visible if the non-free dptfxtract package is also installed.

N/A (not a System Wide Change)

User Experience

- Better performance on certain hardware
- Better cooling of CPUs on certain hardware

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: Don't ship package by default
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change)
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes