> > I launched ovs-dpdk with a single GB of memory on the first numa node
> > (instructions seem to indicate memory should only be allocated to the
> > first numa node... not sure why). When I tried increasing the number
> > of RX queues (ovs-vsctl set Open_vSwitch .
> > other_config:n-dpdk-rxqs=2
> -Original Message-
> From: Traynor, Kevin [mailto:kevin.tray...@intel.com]
>
> > -Original Message-
> > From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of
> > Gabe Black
> > I launched ovs-dpdk with a single GB of memory on the first numa node
> > (instructio
> -Original Message-
> From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of Gabe
> Black
> Sent: Thursday, September 10, 2015 4:08 PM
> To: discuss@openvswitch.org
> Subject: [ovs-discuss] Scaling up ovs-dpdk
>
> So I have been able to profile perf
So I have been able to profile performance with ovs-dpdk on multi-node and
single node servers. However, when I scale up the number of VMs on the compute
nodes, I see a corresponding drop in individual VM performance.
I launched ovs-dpdk with a single GB of memory on the first numa node
(instr
