Dne 13.7.2016 v 12:16 Imobach González Sosa napsal(a):
It sounds good. But it will depend in how much memory is used to make the compression (as you said in a status call IIRC).
My comment was mainly about the `xz` compression tool, according to this [1] document it takes roughly 10 times more RAM than gzip. But the Zlib Ruby compression uses the gzip algorithm so it should be OK regarding to the memory consumption. More over the compression would happend quite early in the installation workflow, at that time there should be still enough memory. The most memory critical part is usually when starting the installation (during partitioning and package installation). I did some other space optimizations and Steffen removed duplicates from inst-sys which saved several megabytes of RAM so this SSH config compression is not that important anymore. But as I wrote before it's really trivial to implement it so I'd look at it again later... Lada [1] http://catchchallenger.first-world.info/wiki/Quick_Benchmark:_Gzip_vs_Bzip2_... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org