From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-yx0-f175.google.com ([209.85.213.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SpcbM-0001XH-05 for openembedded-core@lists.openembedded.org; Fri, 13 Jul 2012 11:55:56 +0200 Received: by yenl13 with SMTP id l13so3110152yen.6 for ; Fri, 13 Jul 2012 02:44:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:content-type:x-gm-message-state; bh=RwJR9r8YxsGjKEKdUBud3faMyCsl5cEK0XC9jrjrcxE=; b=Rzhq2TKxA0YIEzoJOE4k+quEe6dLmLVrvtUPqyeD8KzHWM4XIDlOOIdw4OBmGcKP1E OK+3DxL/QMmHgXPCDnUJrq8qIUeJSuXni689EFK11t3jFu2HKHZy+s2xpp3mh0obNFBb xYbEML8Am0B51BLa2akYxWZX1h5GovsT13yDX6MlQm6uKcAbj+jBCuaJectnltEyC+yb ITdVwFQ+4dAyxuIRZ07RqE3nlZCz5pSzodi0GiLKdf/i0xh8V1r2tbeTPRuF39jloUzL Rd4n3h2jwpbYVU25jfClto9b9/XRHezacN0rlmx4nhSMjbeHzvm9CX0qMJkKH7bfAQV5 +Vcw== Received: by 10.50.40.193 with SMTP id z1mr368732igk.0.1342172681256; Fri, 13 Jul 2012 02:44:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.98.162 with HTTP; Fri, 13 Jul 2012 02:44:21 -0700 (PDT) X-Originating-IP: [89.121.200.106] In-Reply-To: References: <8586287A-0F78-4778-8491-B8E1C70644B1@dominion.thruhere.net> <4FFF23E2.5040007@linux.intel.com> <54ABEC81-9673-446D-AD9A-79394DEEA6E8@dominion.thruhere.net> From: Andrei Gherzan Date: Fri, 13 Jul 2012 12:44:21 +0300 Message-ID: To: Patches and discussions about the oe-core layer X-Gm-Message-State: ALoCoQmt8vN9jBYcP4YwFyp5r4gliUyqbLefnECp9o7MNFc9vRrt9hy/7lbRyg4h0tv5R7d/gF+1 Subject: Re: [PATCH 0/3] Fix xz compression command and optimize compression time X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 09:55:56 -0000 Content-Type: multipart/alternative; boundary=14dae9340c41e4bd1b04c4b2edf7 --14dae9340c41e4bd1b04c4b2edf7 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jul 13, 2012 at 11:19 AM, Andrea Adami wrote: > On Fri, Jul 13, 2012 at 8:45 AM, Koen Kooi > wrote: > > > > Op 12 jul. 2012, om 21:22 heeft Saul Wold het volgende geschreven: > > > >> On 07/12/2012 11:58 AM, Koen Kooi wrote: > >>> Any volunteers to test this on a system with >4 real cores? > >>> > >> > >> Koen, > >> > >> Does OE-Core or Poky have an image setup for using .xz by default? > > > > No, and as you can see from Andrei's patches, it would have never worked > :) > > > > regards, > > > > Koen > > > > This leads to a similar remark for lzma: > > The xz/lzma have been added with commit 38334ac and at that time both > where using XZ_COMPRESSION_LEVEL. > > The code has been refactored afterwards and what happened is that lzma > now defaults to compression 7 (the default) while xz is way too high > (default is 6). > > Nope. It's default value is -9. > There is a well hidden pitfall with that, being that any image, > including the initramfs, will use that compression factor. > > As you can notice in that (old) man xz [2] the memory requirements > What old version? > are very high and what did happen to me was that the cpio.lzma could > not be decompressed thus kernel could not boot (we override now the > value setting "-e2" in our BSP). > > Without threads, memory demand was around 700mb. So it should be ok for most of machines. Adding more threads will multiply that figures. > > Indeed. With 8GB memory at my disposal i couldn't compress an image with -e -9 and -T 0 (-T 4)/ @g --14dae9340c41e4bd1b04c4b2edf7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Fri, Jul 13, 2012 at 11:19 AM, Andrea Adami <= span dir=3D"ltr"><andrea.adami@gmail.com> wrote:
On Fri, Jul 13, 2012 at 8:45 AM, Koen Kooi <koen@dominion.thruhere.net> wrot= e:
>
> Op 12 jul. 2012, om 21:22 heeft Saul Wold het volgende geschreven:
>
>> On 07/12/2012 11:58 AM, Koen Kooi wrote:
>>> Any volunteers to test this on a system with >4 real cores?=
>>>
>>
>> Koen,
>>
>> Does OE-Core or Poky have an image setup for using .xz by default?=
>
> No, and as you can see from Andrei's patches, it would have never = worked :)
>
> regards,
>
> Koen
>

This leads to a similar remark for lzma:

The xz/lzma have been added with commit =A038334ac and at that time both where using XZ_COMPRESSION_LEVEL.

The code has been refactored afterwards and what happened is that lzma
now defaults to compression 7 (the default) while xz is way too high
(default is 6).


Nope. It's default value is -9.
=A0
There is a well hidden pitfall with that, being that any image,
including the initramfs, will use that compression factor.

As you can notice in that (old) man xz [2] =A0the memory requirements

What old version?
=A0
are very high and what did happen to me was that the cpio.lzma could
not be decompressed thus kernel could not boot (we override now the
value setting "-e2" in our BSP).

=A0
Without threads, memory demand was arou= nd 700mb. So it should be ok for most of machines.=A0

<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex"> Adding more threads will multiply that figures.


Indeed. With 8GB memory at my disposal= i couldn't compress an image with -e -9 and -T 0 (-T 4)/
@g
--14dae9340c41e4bd1b04c4b2edf7--