bhouse-nexthop commented on PR #14136: URL: https://github.com/apache/cloudstack/pull/14136#issuecomment-5717278413
> Instead of deriving the count unconditionally, could we make it configurable per system/router service offering? A detail on the offering (read into nic.multiqueue.number, still letting an explicit per-VM value win) would keep your CPU-derived default for anyone who sets -1, let an operator pin an explicit N, and leave it off when unset — which also covers the "no way to turn this off" note. The offering size is pretty small at 1 cpu, which likely most people are sticking with. I know cloudstack likes knobs for everything, and I found out the hard way on a lot of things since there is no documentation on 'recommended knobs to turn on'. I honestly don't see harm in this ... but if its a requirement I can add yet another knob to bit someone else in the future. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
