The taskset value is uses is defined by the DCD_CPU_AFFINITY environment variable in the delta.profile. on boxes which are not running KX Control. The Daemon is a Java process which is used to start processes on remote boxes, i.e. The above setting will set KDB_CPU_AFFINITY to 0-9 in delta.profile Daemon The value of KDB_CPU_AFFINITY can be configured in and nfig which can be passed to the installKxPlatform.sh script (via -p) as follows: kdb-cpu-affinity=0-9
This effectively gives KX Control its own core. This will result in KDB_CPU_AFFINITY being set to core 0 and the process instance taskset values being set to 1-9. The bundle installer will prompt for the number of licensed kdb+ cores, the value you give will result in a taskset range for the same number of cores. The value of KDB_CPU_AFFINITY can be configured at install time as follows: The taskset value it uses is defined by the KDB_CPU_AFFINITY environment variable in the delta.profile. KX Control is a kdb+ process which is run under taskset. Java processes are typically multi threaded and can make use of multiple cores inside a taskset range. Kdb+ is single threaded so when it is taskset to a range of cores the OS scheduler will assign it one core from that range. For example on an 8 core box you can specify a taskset that uses ½ the available cores using the mask 0-3 or 4-7.Īnother aim of task setting is to protect critical processes from being swapped out by other processes on the same box, this can be achieved by task setting the critical process to a given core and omitting that core in all other taskset ranges. Typically we use taskset to give a process a range of cores it can run on. Affinity commandĬPU cores can be identified via an integer on Linux see below: CPU ID
On some Linux systems there is also the option of running kdb+ under numactl (if enabled).
By default the q binary will be run under taskset on Linux. Kdb+ is typically licensed to run on a number of CPU cores. Core affinity Linux CPU afinity configuration
0 kommentar(er)
