tools4j / mmap / 41296024373

push

github

Add CPU pinning for mapping runtimes and perf threads, extract appender ID pool

- CpuPinning (api) pins the calling thread to a CPU, returning a CpuBinding that restores the previous affinity
  when closed by the bound thread; threadFactory(..) creates thread factories pinning each thread to a different
  CPU of a list, in order of preference. Pinning uses Agrona's ThreadAffinity (Linux x86_64/aarch64) and never
  throws: unsupported platforms or OS refusal report a warning and the thread runs unpinned
- Mapping runtime threads are pinned via mmap.mapping.async.mappingRuntimeCpus (Linux cpulist, default NONE);
  AsyncRuntime and AsyncRuntimeInstances accept a ThreadFactory
- AsyncMappingConfigurator.mappingRuntimeUsing(..) takes a single argument, idle strategy and thread factory
  combine through chaining; configurators create runtimes through AsyncRuntimeInstances
- AtomicIdBitSet holds the lock-free lowest-free-ID bit set; IdPool256 moved to mmap-queue as AppenderIdPool
  (owning validateMaxAppenders), IdPool64 and the IdPool interface removed
- ConstantDescribable for named sources of reported events
- Static-only classes are enums without constants
- mmap-perf: --pin [cpus] pins senders, receivers and then mapping runtime threads, one CPU each

1807 of 2072 branches covered (87.21%)

Branch coverage included in aggregate %.

252 of 274 new or added lines in 20 files covered. (91.97%)

5005 of 5337 relevant lines covered (93.78%)

4.02 hits per line