n Behalf Of Prashant
> Upadhyaya
> Sent: Monday, June 10, 2019 6:13 AM
> To: Dave Barach (dbarach)
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Approximate effective CPU utilization of VPP worker
>
> Hi Dave,
>
> Thanks for your suggestion.
>
> As an attempt
Dave
-Original Message-
From: vpp-dev@lists.fd.io On Behalf Of Prashant Upadhyaya
Sent: Monday, June 10, 2019 6:13 AM
To: Dave Barach (dbarach)
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Approximate effective CPU utilization of VPP worker
Hi Dave,
Thanks for your suggestion.
As a
Hi Dave,
Thanks for your suggestion.
As an attempt towards an alternate strategy, I did go ahead and make a
change in the main loop of VPP18.01 (similar change as I describe
below should be valid much in a similar fashion to subsequent
releases) and it seems to be working for me, but there might
The instantaneous vector size - in the stats segment, per-thread - is the best
measure of how hard vpp is working.
It's not a linear function of the offered load, but for any given offered load
/ feature set you can model it with three segments:
* Dead asleep: vector size < 3, offered l
