On Mon, Nov 26, 2018 at 3:03 PM Peter Robinson <pbrobinson(a)gmail.com> wrote:
There's no facts or details, to quote "The reported speed
transactions is substantial. This may solve (or greatly reduce) the
compose speed problem, TBD." but it doesn't report the context of the
"speed increase for transactions" .... like which transactions?
There's a lot of I/O heavy processes in the compose, like createrepo,
that don't run any rpm tracsactions what so ever.
Paul was referring to image creation here. We should be able to get a
fairly significant (at least one order of magnitude) speed-up on
creating any image that runs an RPM installation transaction. I'm not
sure how much that will save in the *whole* compose process, but as
it's an identified spot where we know how to optimize it, we should do