@syncer In my opinion, it is better to have a CLI that can process network interrupts only by the local NUMA node.
As I remember, the set system option performance xxx option overrides some sysctl options if it is not fixed.
Otherwise, we have to use customer scripts to balance interrupts on the required cores.

@Viacheslav, maybe we should just run the script on such platforms instead of doing CLI?

It´s not feasible to implement this.
We may come back to it in 2.0

@syncer What I know only from XEN or XCP-NG was reported
Do no have reports from other platforms

With current changes to build system, this becomes obsolete

too much effort without any benefits

RPI is not our target platform and we don't plan to support it

Closing this, no real benefits and to much effort are required
it's not like we position ourselves as low consumption device. with VPP it will be even worse

Currently I believe that the GraphQL api doesn't offer much functionality unless that has changed over the most recent 3-4 months. I believe it only had get functions and maybe 2 or 3 set methods. This is blocking the web api as it was decided to use GQL for the API.

@Viacheslav so what is the state of this?

No plans to implement it until we receive a request from a customer

Some GRUB options can certainly be useful. I'm against adding ways to pass completely arbitrary options, though. I'll rename the task to reflect that.

Hey @syncer is this feature being bumped to a future release? I saw the Project tags get swapped to a GA tag (which sounds more official to me) but also a comment of "no business case."

@jestabro, what is the current state of this? Should I mark is resolved or keep it?