haproxy/doc/design-thoughts
Willy Tarreau f156baf8ce DOC: design-thoughts: commit numa-auto.txt
Lots of collected data and observations aggregated into a single commit
so as not to lose them. Some parts below come from several commit
messages and are incremental.

Add captures and analysis of intel 14900 where it's not easy to draw
the line between the desired P and E cores.

The 14900 raises some questions (imagine a dual-die variant in multi-socket).
That's the start of an algorithmic distribution of performance cores into
thread groups.

cpu-map currently conflicts a lot with the choices after auto-detection
but it doesn't have to. The problem is the inability to configure the
threads for the whole process like taskset does. By offering this ability
we can also start to designate groups of CPUs symbolically (package, die,
ccx, cores, smt).

It can also be useful to exploit the info from cpuinfo that is not
available in /sys, such as the model number. At least on arm, higher
numbers indicate bigger cores and can be useful to distinguish cores
inside a cluster. It will not indicate big vs medium ones of the same
type (e.g. a78 3.0 vs 2.4 GHz) but can still be effective at identifying
the efficient ones.

In short, infos such as cluster ID not always reliable, and are
local to the package. die_id as well. die number is not reported
here but should definitely be used, as a higher priority than L3.

We're still missing a discriminant between the l3 and cluster number
in order to address heterogenous CPUs (e.g. intel 14900), though in
terms of locality that's currently done correctly.

CPU selection is also a full topic, and some thoughts were noted
regarding sorting by perf vs locality so as never to mix inter-
socket CPUs due to sorting.

The proposed cpu-selection cannot work as-is, because it acts both on
restriction and preference, and these two are not actions but a sequence.
First restrictions must be enforced, and second the remaining CPUs are
sorted according to the preferred criterion, and a number of threads are
selected.

Currently we refine the OS-exposed cluster number but it's not correct
as we can end up with something poorly numbered. We need to respect the
LLC in any case so let's explain the approach.
2025-03-14 18:30:30 +01:00
..
binding-possibilities.txt DOC: commit a few old design thoughts files 2014-06-19 21:02:32 +02:00
connection-reuse.txt DOC: Fix typos in different subsections of the documentation 2018-11-18 22:23:15 +01:00
error-reporting.txt DOC: design: add notes about more detailed error reporting for logs 2024-10-28 17:14:48 +01:00
h2-rx-win.fig [RELEASE] Released version 3.1-dev10 2024-10-16 22:57:52 +02:00
http_load_time.url
numa-auto.txt DOC: design-thoughts: commit numa-auto.txt 2025-03-14 18:30:30 +01:00
pool-debugging.txt DOC: design: add design thoughts for later simplification of the pools 2022-02-24 09:01:59 +01:00
ring-v2.txt DOC: design: write first notes about ring-v2 2024-03-09 11:23:52 +01:00
thread-group.txt CLEANUP: assorted typo fixes in the code and comments 2022-10-30 17:17:56 +01:00