On Tue, Jul 26, 2016 at 3:24 PM, Martin Preisler <mpreisle@redhat.com> wrote:

I found pretty bad inefficiencies in some of our XSLTs.

Check out https://github.com/OpenSCAP/openscap/commit/a65bf27dec4a93e2b87cec8cbcd80bec4fd2328a
or https://github.com/OpenSCAP/openscap/commit/1dd5573b2c964b00af57215cadb7f13b1938bac6

Long story short I was able to cut SSG build time on my machine from
2m21.061s to 1m08.771s. In other words my machine now needs roughly half
the time to build SSG. I was timing `make -j 4`.

It will take a while for these changes to make it into releases
and into distributions but I am writing this email because the
savings are significant and perhaps you want to enjoy them sooner.
SCAP Security Guide contributors are doing a lot of content builds.

This will only work if you !!! have OPENSCAP 1.2.x !!!

If you want to speed up the build, replace

/usr/share/openscap/xsl/xccdf_1.1_to_1.2.xsl with
https://raw.githubusercontent.com/OpenSCAP/openscap/maint-1.2/xsl/xccdf_1.1_to_1.2.xsl

/usr/share/openscap/xsl/xccdf-share.xsl with
https://raw.githubusercontent.com/OpenSCAP/openscap/maint-1.2/xsl/xccdf-share.xsl

and

/usr/share/openscap/xsl/xccdf-guide-impl.xsl with
https://github.com/OpenSCAP/openscap/blob/maint-1.2/xsl/xccdf-guide-impl.xsl


Perhaps it would be worth it to deploy this on our Jenkins slaves
even before it hits releases? What do you think?