'do not pin engine packet processors to dedicated CPU cores' broken

[johndchch]

despite having the option 'do not pin engine packet processors to dedicated CPU cores' selected I can see that eastpect is running ONLY on cpu 0 ( and watching core loading with htop whilst stress testing confirms this )

cpuset -g on the easptect pid gives this :

Eastspect Instance 0 pid= 61127
current cpu affinity
pid 61127 mask: 0
pid 61127 domain policy: first-touch mask: 0

if I manually set the cpu mask to all cores using cpuset I see what I would expect and much more even cpu utilisation at high loads

Eastspect Instance 0 pid= 61127
current cpu affinity
pid 61127 mask: 0, 1, 2, 3, 4, 5, 6, 7
pid 61127 domain policy: first-touch mask: 0

If I un-tick 'do not pin' it sets affinity to cpu 1 as previously, so looks like in the new version there's been some sort of regression in the 'do not pin' code ( ticking it now basically pins the eastpect process to cpu 0 - which is obviously NOT what is intended )

[sy]

Hi,

Can you share config and logs via “Have Feedback” option at the bottom right corner of gui?

[johndchch]

logs etc sent

note that I re-enabled the cron job I used to have prior to the GUI option to un-pin, so if the logs include the current cpuset output for eastspect it'll show it using 0-7 due to the cron job 'un-pinning' the process - without the cron job easpect pins to cpu 0 if 'do not pin' is selected, and defaults back to cpu 1 if 'do not pin' is unticked

[athurdent]

Interesting. I have been waiting for multi core support for a long time now, but according to the roadmap, it’s only 50% and not done yet? https://www.zenarmor.com/roadmap
@sy could you perhaps clarify?

[sy]

Hi,

Multicore support will come with 1.17 release that will be shipped on November.

[athurdent]

Hi,

Multicore support will come with 1.17 release that will be shipped on November.

Awesome! Looking forward to test this with 10G.