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
Add usage of Threads to "xz"-command on archive-routine #1196
Comments
Looks like Thinking we should do this at the same time we address running plugins in parallel, @bmr-cymru @pmoravec |
Running plugins in parallel and this improvement are imho independent on each other but both aiming the same direction - they can just share sosreport's setting of # of threads (that would make sense imho). Why use
|
Yes, makes much more sense. Forgot about python is doing the right math here. |
We'd also want to check to xz version - if a user has an old xz package without this check, we'll fail to create the archive every time. |
Depends on #1199 , once that is merged, we can propose patch here like:
|
Resolves: sosreport#1196 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
Resolves: sosreport#1196 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
Resolves: sosreport#1196 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
In some cases, we need to determine what package provides given binary. This auxiliary function implements it - so far it works for and will be used by archive methods. Related to: sosreport#1196 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
Moving also building of the command from Archive to Plugin class. Resolves: sosreport#1196 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
In some cases, we need to determine what package provides given binary. This auxiliary function implements it - so far it works for and will be used by archive methods. Related to: #1196 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
On systems, with big amount of logfiles, running
sosreport
will take a lot of time.A lot of time is lost during the archiving-process. This could be improved by using threads for
xz
-command easily.A possible way could be to use 20% of the available cores for the archiving process.
The text was updated successfully, but these errors were encountered: