yahoo-eng-team team mailing list archive

[Felix Huettner <2009055@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When creating ~250 ports on a single subnet we currently take around 140
seconds.

This duration increased significantly with the introduction of a fix for
https://bugs.launchpad.net/neutron/+bug/1865891 that exclusively locks a
subnet when a port is created/updated in there.

This was observed in devstack wih ovn as a backend.

Reproducer:

1. Create a network and a subnet
2. Run
```
for i in `seq 1 250`; do  curl -g http://10.1.0.129:9696/networking/v2.0/ports -H "Content-Type: application/json" -H "X-Auth-Token: sometoken" -X POST -d '{"port": {"admin_state_up": true, "name": "test", "network_id": "somenetwork"}}' & done
time wait
```

We see this causing issues on highly frequented subnets (e.g. the ones
hosting our public ips) as the requests take long and die because of our
20 second database max_statement_time.

** Affects: neutron
     Importance: Undecided
     Assignee: Felix Huettner (felix.huettner)
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2009055

Title:
  Performance issue when creating lots of ports

Status in neutron:
  In Progress

Bug description:
  When creating ~250 ports on a single subnet we currently take around
  140 seconds.

  This duration increased significantly with the introduction of a fix
  for https://bugs.launchpad.net/neutron/+bug/1865891 that exclusively
  locks a subnet when a port is created/updated in there.

  This was observed in devstack wih ovn as a backend.

  Reproducer:

  1. Create a network and a subnet
  2. Run
  ```
  for i in `seq 1 250`; do  curl -g http://10.1.0.129:9696/networking/v2.0/ports -H "Content-Type: application/json" -H "X-Auth-Token: sometoken" -X POST -d '{"port": {"admin_state_up": true, "name": "test", "network_id": "somenetwork"}}' & done
  time wait
  ```

  We see this causing issues on highly frequented subnets (e.g. the ones
  hosting our public ips) as the requests take long and die because of
  our 20 second database max_statement_time.

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