All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Joe Slater <jslater@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] webkit-gtk: limit ld memory requirement
Date: Tue, 17 Sep 2013 13:11:56 +0800	[thread overview]
Message-ID: <5237E49C.7090608@windriver.com> (raw)
In-Reply-To: <523501AC.4010208@linux.intel.com>

On 2013年09月15日 08:39, Saul Wold wrote:
> On 09/14/2013 12:10 PM, Burton, Ross wrote:
>> On 14 September 2013 05:35, Khem Raj <raj.khem@gmail.com> wrote:
>>> It does not come with out a price. Have you measured how much 
>>> performance
>>> degradation it brings in ?
>>> We need that to assess the trade off and also describe the machine
>>> configuration where this option is helping
>>
>> Agreed - there's a bug which is tracking this from Kai. As far as I'm
>> aware the failure cases are 32-bit hosts (3GB limit per process) or
>> 64-bit hosts with limited memory. I suggested that we benchmark with
>> and without this - if the performance hit is measured in seconds then
>> we can probably enable it for this recipe out of the box.
>>
> Joe / Kai:
>
> Please test as Khem and Ross suggest and report back with the results, 
> also please include the [YOCTO #5160].

run command 'time bitbake webkit-gtk -c compile' on the host which failed:

without patch till compile fails:
real 49m2.496s
user 102m47.789s
sys 31m18.698s

with the patch:
real 44m9.000s
user 106m45.182s
sys 30m53.223s


On the host build doesn't fail:

Without patch:
real 76m1.646s
user 86m36.704s
sys 38m39.103s

With patch:
real 63m36.193s
user 86m9.274s
sys 37m48.431s

It seems the link option doesn't increase the compile time.

Regards,
Kai

>
> Ross, I am going to assign this to Joe.
>
> Sau!
>
>> Ross
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>
>
>


-- 
Regards,
Neil | Kai Kang



  reply	other threads:[~2013-09-17  5:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 23:28 [PATCH 1/1] webkit-gtk: limit ld memory requirement Joe Slater
2013-09-14  4:35 ` Khem Raj
2013-09-14  8:08   ` Martin Jansa
2013-09-14 19:10   ` Burton, Ross
2013-09-15  0:39     ` Saul Wold
2013-09-17  5:11       ` Kang Kai [this message]
2013-09-17  5:31         ` Khem Raj
2013-09-17 10:30           ` Martin Jansa
2013-09-17 10:53             ` Burton, Ross
2013-09-23 21:51               ` Slater, Joseph
2013-09-24 16:34                 ` Burton, Ross
2013-09-24 16:37                   ` Richard Purdie
2013-09-24 16:39                   ` Khem Raj

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=5237E49C.7090608@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=jslater@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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.