Comment 5 for bug 1463831

Hi Lynn,
will provide my test results by end of the week.
Thanks,
Matthias

Mit TouchDown von meinem Android-Telefon gesendet (www.nitrodesk.com)

-----Original Message-----
From: Lynn [<email address hidden>]
Received: Dienstag, 14 Juli 2015, 0:10
To: Backhausen, Matthias [<email address hidden>]
Subject: [Bug 1463831] Re: neutron DVR poor performance

Tried to reproduce the performance issue.. I ran netperf and tcpdump. I
don't see any packets dropped from network node. Attached result file.

If any performance measurement details/steps can be attached, it would
be a big help.

** Attachment added: "netPerf_tcpdump_results.txt"
   https://bugs.launchpad.net/neutron/+bug/1463831/+attachment/4428436/+files/netPerf_tcpdump_results.txt

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1463831

Title:
  neutron DVR poor performance

Status in neutron:
  Incomplete

Bug description:
  Scenario:
  2 VMs of same tenant but in different subnets talk to each other. The traffic flow is ...

  Traffic VM1 to VM2:
  ========= CN1 ==================== ======== CN2 ===========
  VM1--->br-int--->Router--->br-int--->br-tun---------->br-tun--->br-int--->VM2

  Traffic VM2 to VM1:
  ========= CN2 ==================== ======== CN1 ===========
  VM2--->br-int--->Router--->br-int---br-tun----------->br-tun--->br-int--->VM1

  This works as designed; however obviously br-int of CN1 never gets
  traffic from Router of CN1 (except the very first ARP response), same
  for br-int of CN2. This might lead to flow (or mac?) timeout on br-int
  after 300 secs and degrades performance massively because traffic is
  flooded.

  Changing the mac-addr aging timer influences the issue; change to 30 (default 300) and the issue occurs after 30 seconds (instead 300)
  #ovs-vsctl set bridge br-int other_config:mac-aging-time=30

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1463831/+subscriptions