Linux thread priority/nice set to lower-priority than normal starting from the second benchmark. · dotnet/BenchmarkDotNet#2706

2025-03-10T01:15:01.000Z

I use nice -n -1 when running the benchmark to minimize the effect of background processes on the system (on Linux). I am using NativeAOT 9.0.2 with the InProcessNoEmit toolchain. I observe that when running the first benchmark, the nice value is expectedly -1. However, starting from the second benchmark method, the nice value becomes 10, which is low priority. It is quite surprising to me, but I didn't find where the thread priority is changed.

(7 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)C# (11.415 Stars) (1.054 Forks)batch import

help wantedup-for-grabs

Beschreibung

Dieses Issue enthält keine Beschreibung.

Contributor Guide

Tech Stack: csharp
Domain: performance
Issue Type: bug
Schwierigkeit: 3
Geschätzte Zeit: 1-3 hours
Aktivitätsstatus: active
Klarheit: mostly clear
Voraussetzungen: Basic understanding of BenchmarkDotNetFamiliarity with Linux thread priorityC# knowledge
Einsteigerfreundlichkeit: 50
Research-Richtung: 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.