Linux thread priority/nice set to lower-priority than normal starting from the second benchmark.

Description

This issue does not include a description.

Contributor guide

Tech stack

csharp

Domain

performance

Issue type

bug

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-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

Basic understanding of BenchmarkDotNetFamiliarity with Linux thread priorityC# knowledge

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

50

Research direction

Investigate where the thread priority is changed during benchmark execution. Look at the BenchmarkDotNet source code, particularly in the ProcessRunner or BenchmarkRunner classes. Check if there is any code that sets thread priority or nice values. Also examine how the initial benchmark process is spawned with nice n 1 and why subsequent benchmarks have a different nice level. Look for any thread pool or scheduler settings that might be overridden.