Yes its quite feasible to package binary *.rpm files in parallel.
The hardest problem is choosing a framework for parallelization: OMP, or
pthreads or (in RPM5) yarn.
A general framework for parallelization is needed, with queues and thread pools
and output serialization etc, is needed because there are many simple loops in
RPM that would benefit from being done in parallel.
FWIW: Using OMP on the rpmbuild loop would be the least intrusive but perhaps
hardest to maintain (compared to plain pthreads or yarn from pigz).
(aside)
Before attempting parallelization, there are some costly "sanity checks" on
file manifests in rpm build that are quadratic or worse that should be studied
and fixed (at least in RPM5: I suspect there are some in RPM4 too but haven't
measured recently). Run cache grind on a kernel build (which has lots of files)
to see what I am talking about,
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/211#issuecomment-298955256
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
