Christof Ressi

@sonoro1234 thanks! One question from my side: This PR introduces a new command line option `--thread-pinning`. Unfortunately, `-t` and `-T` are already taken so I just picked `-y` as the...

Hi @dyfer > is thread pinning desirable in general? That's what I want to find out! By default, thread pinning has been always *on* by on Linux, *off* on macOS...

> That may be old information by now though! I think the point is that things can change and it's good being able to adapt quickly. For example, macOS now...

I want to stress again, however, that this PR doesn't change existing behavior. It merely turns something that was hardcoded into a command line option while keeping the defaults (Linux:...

I've updated the PR description to clarify a few things that have come up.

> Well, my question was not hypothetical: is there any (dis)advantage of pinning the single audio thread? I never thought about that. I think the scheduler knows best where the...

Generally, I don't really want to give suggestions or recommendations about thread pinning because I am not an expert on this topic and I didn't do any tests yet. The...

> I've used one of the M1 machines recently and these have both slower ("efficiency") and faster ("performance") cores. This could even be a situation where you might want to...

> A very non-scientific test (looking at the macOS Activity Monitor) suggests that on a 8-core M1 (4 performance + 4 efficiency cores), supernova uses 4 cores by default. That's...

The current default values are now mentioned in `ServerOptions`.