-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixes #25173 - Fix slow enabled report generation #78
Conversation
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
@kevin-bowers thanks for the PR and the thorough analysis. 💯 I currently have another work-in-progress PR (#77) open that will affect this area of the code. Once that is merged (in the next few days hopefully) I'll ask you to rebase this PR. |
@kevin-bowers you can go ahead and rebase - the issue should still be present so your fix is still valid. After that I'll do some testing of my own :) |
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
Just re-based. I like your changes too. I applied the same fix from before. |
It looks like your rebase didn't go quite right. Looking at the 'Commits' tab I see there are 7 commits - one of them in the middle is my recent commit that you wanted to base on top of! I'd expect to see a single commit on this PR with the commit message in the same format as the name of this PR: 'fixes #.....' Might be a good use of interactive rebase from your working copy: |
It looks like I have totally screwed up my branch. Not sure how I did that. I'm going to close this, re-branch, and open a new PR. Sorry about that! |
In its current state, this piece of the
enabled_repos_upload
yum/dnf plugin imports theyum
ordnf
Python module and creates an associated object each time_replace_vars()
is executed. This can lead to time consuming yum operations if there are a large number of enabled yum repositories.Example
A server has 13 enabled yum repositories. With
yum.YumBase()
being re-executed with each run of_replace_vars()
. This results in the following output from a simpleyum check-update
:The output is excessively long and it takes 35 seconds to tell me that nothing is available to update. With this PR in place, it only takes 6 seconds and the output is much shorter: