Tasksets

This page describes taskset configuration for KXS processes, including guidance on CPU selection, NUMA awareness, and license constraints.

Setting tasksets is not recommended. However, it is often required to restrict the cores for q processes to stay within the number of cores supported by the q license. When selecting CPUs:

• Avoid CPU0 and its NUMA sibling. On many Linux systems, CPU0 is the default processor for handling kernel threads and system-level tasks. Network interface cards (NICs), disk I/O, and other hardware interrupts are often routed to CPU0 by default.
• Binding a process to CPUs within the same NUMA node can reduce memory latency and improve performance. Use tools like numactl or lscpu to inspect NUMA topology.
• CPUs sharing the same cache (L2/L3) can benefit from faster data access.

Next steps

• Network conditioning and fast failure detection
• About RT