Thanks bjeremy32 for sharing the patch!
As mentioned by Dave, I have implemented load calculation in a plugin. I can
try to reevaluate my implementation with yours as reference. Will let you know
if I get it working.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
le, after the node->function returns if (
> (VLIB_NODE_TYPE_PRE_INPUT || VLIB_NODE_TYPE_INPUT) && number of packets
> processed == 0) then we count it as idle, else we count it as busy.
>
>
>
>
>
> *From:* Ramkumar B
> *Sent:* Wednesday, December 16, 2020 10:27
ar1...@gmail.com
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Core Load Calculation
>
>
>
> We’ve been using flamegraphs quite successfully to see how much leeway is
> there.
>
>
>
> Ex:
> https://gist.githack.com/mejedi/d5d094df63faba66d413a677fcef26e3/raw
.@gmail.com
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Core Load Calculation
>
>
>
> We’ve been using flamegraphs quite successfully to see how much leeway is
> there.
>
>
>
> Ex:
> https://gist.githack.com/mejedi/d5d094df63faba66d413a677fcef26e3/raw/95294d36c4b180ba6741d
indicator of load, but it does not increase linearly
with PPS. This is because of the VPP's self balancing behaviour where the
cost per packet reduces as load increases. It would be a great help if
anyone can point out factors to calculate load.
Thanks and regards,
Ramkumar Balu
