Comment # 12 on bug 1158474 from Harald Koenig

(In reply to Takashi Iwai from comment #9)
> So, actually what kind of hardware are you testing?

I'm not really testing hardware -- I just try to use my own private notebook:
see very end of original report:

         Lenovo X260 with 2-core Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz,  16
GB ram and Samsung 850EVO SSD.

so not too old to explain what's going on...


> If XZ-decompression takes such extremely long time, we have to address in XZ
> library side.  XZ is used for the packaging itself, so this must be the
> pretty basis.  It's no specific problem to depmod or kernel packaging.

xz is known to be *very* cpu intensive for compression ops -- but this only
happens once on the build server (for this issue, but e.g. not for mkinitrd;)


> Check the standard xz program and see whether it takes longer than other
> systems.  Then try profiling what takes too long on your problematic system.

see my comment #5 for using unxz to uncompress all *.ko.xz files.

anyone else want to provide 'benchmark results' for your platform(s) for this
test ?