Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 512676[details]
reproducer
Description of problem:
ifup on a bridge+vlan, when there are many bridges and vlans with it on the same nic, is very slow. The significant slow-down affects us and the entire software stack.
Version-Release number of selected component (if applicable):
initscripts-9.03.23-1.el6.x86_64
How reproducible:
Quite.
Steps to Reproduce:
1. Edit the constant "NIC" in the attached script to refer to an available network interface (e.g. NIC = "eth1")
2. Run the script with the number of network you want. (e.g. python makenetworks.py 100)
3. Read output
Actual results:
(an extract from the script)
Adding bridge 0 ... Starting ifups... ifups took 0.13 seconds
Adding bridge 10 ... Starting ifups... ifups took 0.18 seconds
Adding bridge 20 ... Starting ifups... ifups took 0.14 seconds
Adding bridge 30 ... Starting ifups... ifups took 0.16 seconds
Adding bridge 40 ... Starting ifups... ifups took 0.17 seconds
Adding bridge 50 ... Starting ifups... ifups took 0.45 seconds
Adding bridge 60 ... Starting ifups... ifups took 0.21 seconds
Adding bridge 70 ... Starting ifups... ifups took 0.22 seconds
Adding bridge 80 ... Starting ifups... ifups took 0.25 seconds
Adding bridge 90 ... Starting ifups... ifups took 0.28 seconds
Adding bridge 100 ... Starting ifups... ifups took 0.31 seconds
Adding bridge 110 ... Starting ifups... ifups took 0.35 seconds
Adding bridge 120 ... Starting ifups... ifups took 0.39 seconds
Adding bridge 130 ... Starting ifups... ifups took 0.43 seconds
Adding bridge 140 ... Starting ifups... ifups took 0.49 seconds
Adding bridge 150 ... Starting ifups... ifups took 0.53 seconds
Adding bridge 160 ... Starting ifups... ifups took 0.59 seconds
Adding bridge 170 ... Starting ifups... ifups took 0.65 seconds
Adding bridge 180 ... Starting ifups... ifups took 0.73 seconds
Adding bridge 190 ... Starting ifups... ifups took 0.80 seconds
Adding bridge 199 ... Starting ifups... ifups took 0.87 seconds
Expected results:
Umm constant performance?
Additional info:
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
In previous version of initscripts, ifup-aliases became slower with increasing number of vlans. This update replaces ifconfig in ip-aliases with ip.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-0816.html
Created attachment 512676 [details] reproducer Description of problem: ifup on a bridge+vlan, when there are many bridges and vlans with it on the same nic, is very slow. The significant slow-down affects us and the entire software stack. Version-Release number of selected component (if applicable): initscripts-9.03.23-1.el6.x86_64 How reproducible: Quite. Steps to Reproduce: 1. Edit the constant "NIC" in the attached script to refer to an available network interface (e.g. NIC = "eth1") 2. Run the script with the number of network you want. (e.g. python makenetworks.py 100) 3. Read output Actual results: (an extract from the script) Adding bridge 0 ... Starting ifups... ifups took 0.13 seconds Adding bridge 10 ... Starting ifups... ifups took 0.18 seconds Adding bridge 20 ... Starting ifups... ifups took 0.14 seconds Adding bridge 30 ... Starting ifups... ifups took 0.16 seconds Adding bridge 40 ... Starting ifups... ifups took 0.17 seconds Adding bridge 50 ... Starting ifups... ifups took 0.45 seconds Adding bridge 60 ... Starting ifups... ifups took 0.21 seconds Adding bridge 70 ... Starting ifups... ifups took 0.22 seconds Adding bridge 80 ... Starting ifups... ifups took 0.25 seconds Adding bridge 90 ... Starting ifups... ifups took 0.28 seconds Adding bridge 100 ... Starting ifups... ifups took 0.31 seconds Adding bridge 110 ... Starting ifups... ifups took 0.35 seconds Adding bridge 120 ... Starting ifups... ifups took 0.39 seconds Adding bridge 130 ... Starting ifups... ifups took 0.43 seconds Adding bridge 140 ... Starting ifups... ifups took 0.49 seconds Adding bridge 150 ... Starting ifups... ifups took 0.53 seconds Adding bridge 160 ... Starting ifups... ifups took 0.59 seconds Adding bridge 170 ... Starting ifups... ifups took 0.65 seconds Adding bridge 180 ... Starting ifups... ifups took 0.73 seconds Adding bridge 190 ... Starting ifups... ifups took 0.80 seconds Adding bridge 199 ... Starting ifups... ifups took 0.87 seconds Expected results: Umm constant performance? Additional info: