Pinning DRBD Proxy to Specific CPU Core(s)
This article will explain how you can pin DRBD Proxy to a single CPU Core. This might be used with a DRBD® CPU-mask for more efficient DRBD to DRBD Proxy replication.
Pinning DRBD Proxy to a single CPU Core can help speed things along by keeping all the DRBD Proxy memory uniformly accessible.
Refer to the man 8 drbd-proxy section “CPU usage control”.
Create a file, /etc/default/drbdproxy, with the following setting:
DRBD_PROXY_CPU_COUNT=6
…or, even better, use a CPU mask value:
DRBD_PROXY_CPU_MASK=0x030f
The magic is in the init script, so you can copy the init script from DRBD
Proxy 3.2.3 or later version to an older version of DRBD Proxy to get it to read
/etc/default/drbdproxy.
Please consult taskset or lstopo for more details. The quick version: Use
the following command to output the numa topology in taskset format (because
that’s what DRBD Proxy expects), and select the CPUset that you want to use:
# lstopo-no-graphics -c --taskset
Reviewed 2020-12-01 – DGT
Updated 2025-01-28 - JRC