From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Joe Slater <jslater@windriver.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] webkit-gtk: limit ld memory requirement
Date: Tue, 17 Sep 2013 12:30:29 +0200 [thread overview]
Message-ID: <20130917103029.GA7313@jama> (raw)
In-Reply-To: <CAMKF1sqDxGyVnrap0=Jsq=iMFGnXkupjuWnTSwxzBv8K4tqzPg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
On Mon, Sep 16, 2013 at 10:31:18PM -0700, Khem Raj wrote:
> On Mon, Sep 16, 2013 at 10:11 PM, Kang Kai <Kai.Kang@windriver.com> wrote:
> > 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.
>
> on the contrary its reducing the build time which is kind of
> interesting and seems a win-win. are you able to extract the failing
> link command and just run that with/without the linker option to
> discard memory ? and measure just the linking time on the host where
> it already builds without this option?
I think someone should measure it on machine with a lot of ram. If the
test was executed on machine where it was linking mostly from swap,
then it's not so surprising it was faster with the option enabled.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-09-17 10:28 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
2013-09-17 5:31 ` Khem Raj
2013-09-17 10:30 ` Martin Jansa [this message]
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=20130917103029.GA7313@jama \
--to=martin.jansa@gmail.com \
--cc=jslater@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox