Bug 1029786 - RFE: run compression utilities in a multithread way
Summary: RFE: run compression utilities in a multithread way
Keywords:
Status: POST
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: dracut-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-13 08:33 UTC by Vratislav Podzimek
Modified: 2016-03-28 22:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
Patch for running xz and lzma in multiple threads (1.01 KB, patch)
2013-11-13 09:16 UTC, Vratislav Podzimek
no flags Details | Diff

Description Vratislav Podzimek 2013-11-13 08:33:56 UTC
Description of problem:
dracut runs compression utilities in various places. And while xz/lzma has the -T option to tell number of threads they should use and there is 'pigz' as a parallel version of gzip, dracut doesn't make use of that. Changing those calls would significantly speed up processing on multicore machines.

Version-Release number of selected component (if applicable):
dracut-034-24.git20131030.fc21.x86_64

How reproducible:
100 %

Steps to Reproduce:
1. run dracut
2. run 'top' to see that the forked 'xz' process uses at most 100 % CPU

Actual results:
compression done using one thread only

Expected results:
compression done using as much threads as possible

Comment 1 Vratislav Podzimek 2013-11-13 09:04:34 UTC
Oh I see, pigz is already used.

gzip)  compress="gzip -9"; command -v pigz > /dev/null 2>&1 && compress="pigz -9";;

Comment 2 Vratislav Podzimek 2013-11-13 09:16:57 UTC
Created attachment 823305 [details]
Patch for running xz and lzma in multiple threads

Comment 4 Mike McCune 2016-03-28 22:31:02 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions


Note You need to log in before you can comment on or make changes to this bug.