qpsolvers/qpbenchmark

CPU thermal throttling

Open

#88 opened on Nov 22, 2023

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (19 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (181 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your proposal related to a problem?

From https://github.com/qpsolvers/qpsolvers_benchmark/discussions/87:

Unless very efficiently cooled, modern CPU cannot run at max speed for long. This can considerably skew timings.

Describe the solution you'd like

Make sure the benchmark solves all problem with consistent performance, monitoring and reacting to thermal throttling.

Describe alternatives you've considered

  • Monitoring throttling state between solver calls (pro: single thread, con: throttling may happen during a solver call)
  • Downscaling to e.g. 50% of the total CPU performance to lower the probability throttling happens

Additional context

See https://github.com/qpsolvers/qpsolvers_benchmark/discussions/87.

Contributor guide

Research direction
Research how the benchmark currently measures solver timings, and investigate methods to detect CPU thermal throttling (e.g., reading CPU frequency or temperature). Explore how to integrate throttling monitoring and decide on a response strategy.
Tech stack
python
Domain
performance
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55