Bug 1029786

Summary: RFE: run compression utilities in a multithread way
Product: [Fedora] Fedora Reporter: Vratislav Podzimek <vpodzime>
Component: dracutAssignee: dracut-maint
Status: POST --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dracut-maint, harald, jonathan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch for running xz and lzma in multiple threads none

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 3 Harald Hoyer 2013-11-13 12:22:30 UTC 
http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=a3bfaa191958c4b70d6c674f972c3b911f8b1bfa
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