Running on 2 sibling threads on haswell/bradwell usually gives around 10% more 
performance, and on skylake/cascadelake number is 20% or more.
Caveat is that you need to rely on RSS or some other mechanism do equally 
distribute traffic between 2 cores….

— 
Damjan


> On 17 Apr 2020, at 09:12, Benoit Ganne (bganne) via lists.fd.io 
> <bganne=cisco....@lists.fd.io> wrote:
> 
> Hi Prashanth,
> 
> It depends of your CPU. We usually recommend to disable hyperthreading for 
> Haswell, but to enable it for Skylake and Cascade Lake. When enabled, you 
> should run 2 workers per physical core, 1 per hyper-thread. You can find more 
> details here: 
> https://www.lfnetworking.org/resources/2019/03/08/benchmarking-software-data-planes-intel-xeon-skylake-vs-broadwell1/
> 
> Best
> ben
> 
>> -----Original Message-----
>> From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Prashanth
>> Candade via lists.fd.io
>> Sent: jeudi 16 avril 2020 10:57
>> To: vpp-dev@lists.fd.io
>> Subject: [vpp-dev] VPP and Core allocation
>> 
>> Hello,
>> 
>> We are integrating VPP into our product.
>> 
>> One question we had was about the recommendation for usage of cores.
>> 
>> 
>> 
>> When using DPDK, the recommendation is to allocate it one physical core.
>> 
>> When using HyperThreaded cores, for DPDK one core is allocated and sibling
>> core is not allocated to anyone.
>> 
>> 
>> 
>> For VPP do we have any such recommendation?
>> 
>> Should we assign VPP to a specific vcore and not assign the sibling core
>> to any other thread or process?
>> 
>> 
>> 
>> Regards,
>> 
>> Prashanth
>> 
>> ________________________________
>> 
>> This e-mail message may contain confidential or proprietary information of
>> Mavenir Systems, Inc. or its affiliates and is intended solely for the use
>> of the intended recipient(s). If you are not the intended recipient of
>> this message, you are hereby notified that any review, use or distribution
>> of this information is absolutely prohibited and we request that you
>> delete all copies in your control and contact us by e-mailing to
>> secur...@mavenir.com. This message contains the views of its author and
>> may not necessarily reflect the views of Mavenir Systems, Inc. or its
>> affiliates, who employ systems to monitor email messages, but make no
>> representation that such messages are authorized, secure, uncompromised,
>> or free from computer viruses, malware, or other defects. Thank You
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#16094): https://lists.fd.io/g/vpp-dev/message/16094
Mute This Topic: https://lists.fd.io/mt/73066645/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to