All of lore.kernel.org
 help / color / mirror / Atom feed
From: McClintock Matthew-B29882 <B29882@freescale.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Fix xz compression command and optimize compression time
Date: Thu, 12 Jul 2012 19:20:28 +0000	[thread overview]
Message-ID: <CAEsOVNdmS9eFrdRbx4_9+RqEzr6=CAWmAwPo_4wNLYAEvyekVg@mail.gmail.com> (raw)
In-Reply-To: <8586287A-0F78-4778-8491-B8E1C70644B1@dominion.thruhere.net>

On Thu, Jul 12, 2012 at 1:58 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> Any volunteers to test this on a system with >4 real cores?

How do you get the memory usage bit?

-M

>
> Op 12 jul. 2012, om 20:13 heeft Andrei Gherzan het volgende geschreven:
>
>> Koen suggested to add -T to xz commands. We have this option implemented in our current version .1alpha.
>>
>> -T threads, --threads=threads
>>              Specify the number of worker threads to use.  Setting threads to
>>              a special value 0 makes xz use as many threads as there are  CPU
>>              cores  on  the system.  The actual number of threads can be less
>>              than threads if the input file is not big enough  for  threading
>>              with  the  given  settings or if using more threads would exceed
>>              the memory usage limit.
>>
>> -------------------
>>
>> Memory: 7.8 GiB
>> Processor:: Intel® Core™ i5-2540M CPU @ 2.60GHz × 4
>>
>> File to compress: 1.9G
>>
>> xz -f -k -e -9 --check=crc32 (current configuration)
>> Memory: 673Mb
>> real    6m37.170s
>> user    6m35.389s
>> sys     0m0.884s
>> Compressed file size: 3.4Mb
>>
>> xz -f -k -e -9 -T 4 --check=crc32
>> Memory: Cannot allocate memory
>>
>> xz -f -k -e -8 -T 4 --check=crc32
>> Memory: 1.8G
>> real    3m24.462s
>> user    12m8.502s
>> sys     0m2.180s
>> Compressed file size: 3.4Mb
>>
>> xz -f -k -T 4 --check=crc32 (-e defaults to -6)
>> Memory: 471Mb
>> real    1m9.265s
>> user    4m8.972s
>> sys     0m0.944s
>> Compressed file size: 3.4Mb
>>
>> So my conclusion would be to use the default -e -6 with -T 0.
>>
>> The following changes since commit 90ad663909c0c8a405b22a510c9f957007d02669:
>>
>>  upstream_tracking: update boost (2012-07-09 17:21:38 +0100)
>>
>> are available in the git repository at:
>>
>>  git://git.yoctoproject.org/poky-contrib ag/xz
>>  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ag/xz
>>
>> Andrei Gherzan (3):
>>  image_types.bbclass: Fix COMPRESS_CMD for xz to redirect compressed
>>    data to file
>>  image_types.bbclass: Add XZ variable to set number of threads to be
>>    used while compressing
>>  image_types.bbclass: Default XZ_COMPRESSION_LEVEL to -e -6
>>
>> meta/classes/image_types.bbclass |    5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> --
>> 1.7.9.5
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



  reply	other threads:[~2012-07-12 19:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 18:13 [PATCH 0/3] Fix xz compression command and optimize compression time Andrei Gherzan
2012-07-12 18:13 ` [PATCH 1/3] image_types.bbclass: Fix COMPRESS_CMD for xz to redirect compressed data to file Andrei Gherzan
2012-07-12 18:13 ` [PATCH 2/3] image_types.bbclass: Add XZ variable to set number of threads to be used while compressing Andrei Gherzan
2012-07-12 18:13 ` [PATCH 3/3] image_types.bbclass: Default XZ_COMPRESSION_LEVEL to -e -6 Andrei Gherzan
2012-07-12 18:58 ` [PATCH 0/3] Fix xz compression command and optimize compression time Koen Kooi
2012-07-12 19:20   ` McClintock Matthew-B29882 [this message]
2012-07-12 19:22   ` Saul Wold
2012-07-12 19:59     ` Andrei Gherzan
2012-07-12 20:14       ` Khem Raj
2012-07-13  6:45     ` Koen Kooi
2012-07-13  8:19       ` Andrea Adami
2012-07-13  9:44         ` Andrei Gherzan
2012-07-13  9:54           ` Andrea Adami
2012-07-13  9:59             ` Andrei Gherzan
2012-07-17 16:27 ` Saul Wold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEsOVNdmS9eFrdRbx4_9+RqEzr6=CAWmAwPo_4wNLYAEvyekVg@mail.gmail.com' \
    --to=b29882@freescale.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.