Description of problem:
We added 6000 hosts to satellite/capsule. Each capsule has 2 to 2.5k content hosts. Start changing location of few content hosts (500) using hammer.
hammer --username admin --password changeme host update --name gprfc20.container3.example.com --location-id 5
Open content-hosts UI page takes more than > 38 sec
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. initiate changing location of 500 content hosts
2. open content-hosts page (where 6k registered)
UI takes > 38 sec
UI should take lesser time
This bugzilla is discussing 2 different performance issues (content hosts and remote execution). I am going to clone this bugzilla so that the 2 issues may be tracked separately.
Tested on 6.3.0. Registered 6000 hosts. Content host page took between 1 and 4 seconds to render. Ran:
for i in `seq 100 600`; do hammer host update --id=$i --location-id=3; done
Accessed the content host page a few times. Took between 1 and 4 seconds still.
Closing since i cannot reproduce on 6.3.0. If you still experience the content hosts slowness, please feel free to reopen with more details. Thanks!