-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-06-21 03:03, Yamaban wrote:
On Sat, 21 Jun 2014 02:47, Carlos E. R.
wrote:
It could be a choice, but not the default, IMO.
Valid point, how about something similar to the locatedb update script:
[CODE] nice -n 19 ionice -c 3 $PACKER ..... [/CODE]
that should limit the impact of the PACKER on the system, no matter of xz or pixz are used.
That results in this task filling up all the remaining cpu power left by the primary tasks. Ie, the computer get used 100%. The user would not feel it, but it also has the side effect of heating the computer more and using more electricity (way more important on laptops). I do not have proof of this, but a certain task using a minute at 100% CPU uses more electricity than the same task done at 50% CPU (or rather at the lower frequency setting of the CPU) during 2 minutes. I see several possibilities. Using a configurable nice value. Using a configurable number of cores, or percent of total cores. Using cpulimit or equivalent tool (it works better than "nice"). Adding ionice -c 3 on config (useful for disk intensive tasks). And all periodic and intensive cron jobs could use these global settings. For the moment, I would be quite content with having this particular cronjob just using xz instead of gzip, same as logrotate does :-) It seems a trivial change to do. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOk4BQACgkQtTMYHG2NR9VEtwCdHNRn4YxhlJyz+GcHVSp6CQVt HZkAn1L2Oy2aamzzYt19jjicuqZACwpf =29z4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org