libvma icon indicating copy to clipboard operation
libvma copied to clipboard

VMA_INTERNAL_THREAD_AFFINITY doesn't run the vma internal thread on the specified core

Open boranby opened this issue 7 months ago • 4 comments

Subject

running with: LD_PRELOAD=libvma.so VMA_SPEC=latency VMA_INTERNAL_THREAD_AFFINITY=2 ./app However, VMA internal thread run on the same core with the application. I tried to use bit-mask approach to set the affinity it also didn't work.

Issue type

  • [x] Bug report
  • [ ] Feature request

Configuration:

  • Product version VMA-9.8.51
  • OS RHEL 9.4
  • OFED MLNX_OFED_LINUX-24.04-0.6.6.0
  • Hardware Mellanox MT2894 Family [ConnectX-6 Lx]

Actual behavior:

VMA_INTERNAL_THREAD_AFFINITY=2 doesn't have an impact on the core affinity of the vma process. It's running on the same core with the application thread. Causing context switches and hanging which impact the latency.

Expected behavior:

The recommended configuration is to run VMA internal thread on a different core than the application but on the same NUMA node. To achieve this VMA_INTERNAL_THREAD_AFFINITY should work as expected to pin the vma process to the core we want it to be.

Steps to reproduce:

boranby avatar Jul 10 '24 09:07 boranby