On Thu, May 29, 2014 at 12:36 AM, Ben Pfaff wrote:
> On Wed, May 28, 2014 at 12:04 AM, lin shaopeng wrote:
> > Some heads up, we changed our flow idle_timeout to 300, then ran the test
> > again, and got around 6000 packet-in per second.
> > After some investigation, it turns out that most of th
On Wed, May 28, 2014 at 12:04 AM, lin shaopeng wrote:
> Some heads up, we changed our flow idle_timeout to 300, then ran the test
> again, and got around 6000 packet-in per second.
> After some investigation, it turns out that most of the ovs-vswitchd CPU
> cycles are consumed
> by add flow, like
Thank you for your reply, Ben.
Some heads up, we changed our flow idle_timeout to 300, then ran the test
again, and got around 6000 packet-in per second.
After some investigation, it turns out that most of the ovs-vswitchd CPU
cycles are consumed
by add flow, like classifier_rule_overlaps(),
minif
On Mon, May 26, 2014 at 09:55:33PM +0800, lin shaopeng wrote:
> I am currently running tests to test packet-in performance of OVS
> (ovs-2.0.1).
> By starting up a large number of different connections simultaneously,
> causing a bunch of packet-in messages sent to the controller. It turns
> out th
Hi everyone,
I am currently running tests to test packet-in performance of OVS
(ovs-2.0.1).
By starting up a large number of different connections simultaneously,
causing a bunch of packet-in messages sent to the controller. It turns
out that OVS can only handle about 3000 packet-in messages per s