Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: World builds HW Was: [PATCH 04/12] gnome-icon-theme: remove the recipe
Date: Wed, 14 Oct 2015 15:01:00 +0200	[thread overview]
Message-ID: <20151014130100.GB22448@jama> (raw)
In-Reply-To: <561D6D00.4050702@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 5169 bytes --]

On Tue, Oct 13, 2015 at 04:43:44PM -0400, Randy MacLeod wrote:
> On 2015-09-18 01:56 PM, Tom King wrote:
> > Martin, Randy et.al <http://et.al>.:
> >
> > I'm moving around things such that I can give Martin a full builder:
> >
> > 24Cores, 256GB RAM,  up to 3TB storage from the donation that HP made to
> > WebOS-Ports (as I consider it essential to webOS-Ports that OE has a
> > strong foundation)
> >
> > Tom
> 
> Thanks Tom.
> I'm back from vacation, cleaning up old emails.
> 
> Did the upgrade help Martin?

I'm still waiting for access to that server.

> Do you need additional systems?

More builders are always welcome. In ideal case I would trigger all 3
architectures in parallel on different builders.

> ../Randy
> >
> > On Fri, Sep 18, 2015 at 10:30 AM, Martin Jansa <martin.jansa@gmail.com
> > <mailto:martin.jansa@gmail.com>> wrote:
> >
> >     On Fri, Sep 18, 2015 at 12:24:00PM -0400, Randy MacLeod wrote:
> >      > On 2015-09-07 11:14 AM, Martin Jansa wrote:
> >      > > Full jenkins build test takes over 3 days (depending on sstate
> >     reuse,
> >      > > one MACHINE can take more than 24 hours), so if I add them to
> >      > > master-next after it's merged to oe-core it will take 3-6 days to
> >      > > build-test them (6 days if they are sent just after current
> >     queue is
> >      > > sent for build).
> >      >
> >      > Hi Martin,
> >
> >     Hi Randy,
> >
> >      > Replying privately but you can add the list back in your
> >      > reply if you like.
> >
> >     OK, adding both MLs
> >
> >      > I never build all of meta-oe but a day seems like a long time.
> >      > On a 3-4 year old 24 core system, with 64 GB RAM and
> >      > 2 large disks, I build oe-core + a whitelist of meta-oe + misc
> >     layers in
> >      > 5 hours using 18.3 of the 24 cores on average.
> >      > What are the specs of your build machine?
> >
> >     It's one of VMs running on box donated by HP to webos-ports project. It
> >     has access to 8 E5-2630L 0 @ 2.00GHz cores (from IIRC 24) and slow IO
> >     which we try to compensate a bit by using tmpfs for TMPDIR, VM has 80G
> >     RAM, so I'm using 72G for tmpfs.
> >
> >     Tom: please fill-in the gaps, I don't know any details about the real HW
> >     it's running on.
> >
> >     The same machine is also running some webos-ports builds sometimes.
> >
> >     BUT be aware that my world build is much bigger than what you're
> >     probably building and changes in oe-core almost always ensure very low
> >     sstate reuse.
> >
> >     e.g. last build with only small oe-core upgrade since previous build:
> >     NOTE: Tasks Summary: Attempted 33283 tasks of which 5252 didn't need
> >     to be rerun and 33 failed.
> >     NOTE: Build completion summary:
> >     NOTE:   do_populate_sysroot: 21% sstate reuse (485 setscene, 1750
> >     scratch)
> >     NOTE:   do_package_qa: 12% sstate reuse (262 setscene, 1760 scratch)
> >     NOTE:   do_package: 4% sstate reuse (76 setscene, 1750 scratch)
> >     NOTE:   do_packagedata: 13% sstate reuse (281 setscene, 1750 scratch)
> >     NOTE:   do_package_write_ipk: 12% sstate reuse (262 setscene, 1756
> >     scratch)
> >     NOTE:   do_populate_lic: 22% sstate reuse (521 setscene, 1806 scratch)
> >
> >     real    1485m40.070s
> >     user    4166m49.125s
> >     sys     2825m50.068s
> >
> >     BTW: you can see all this information in the world logs I'm sending
> >     to MLs
> >     (but not all the builds make it to ML report).
> >
> >      > A decent build box these days has 32+ cores, 64+ GB RAM  and
> >      > and SSD or RAID disk filesystem. The costs of such a system
> >      > are significant but worth it given the number of people's time
> >      > involved in meta-oe.
> >
> >     That's true, but I have to do with what I have available :).
> >
> >      > Also, it would be nice if OE had a few such machines each
> >      > working on builds for a MACHINE to reduce your turn-around
> >      > to more like a day or so. :)
> >
> >     Yes, it would be nice, I'm trying to get Tom King to set another VM like
> >     this in another location (another HP donated server), hopefully he will
> >     finish it soon.
> >
> >     It's all hosted together with OE infrastructure, bandwidth is
> >     limited, but
> >     all I need for these builds is to fetch sources and upload the logs,
> >     there
> >     are no package feeds or sstate from these builds usable outside, but
> >     now it
> >     rsync the downloaded sources to sources.openembedded.org
> >     <http://sources.openembedded.org>
> >
> >     If you know about some idling build servers, I would like to give them
> >     something to do :).
> >
> >     Regards,
> >
> >     --
> >     Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
> >     <mailto:Martin.Jansa@gmail.com>
> >
> >
> 
> 
> -- 
> # Randy MacLeod. SMTS, Linux, Wind River
> Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, 
> Canada, K2K 2W5

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-10-14 13:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 15:34 [PATCH 00/12] Various package/RRS updates Alexander Kanavin
2015-09-03 15:34 ` [PATCH 01/12] ccache: update to 3.2.3 Alexander Kanavin
2015-09-03 15:34 ` [PATCH 02/12] mailx: update to 12.5-5 Alexander Kanavin
2015-09-03 15:34 ` [PATCH 03/12] net-tools: update to 1.60-25 Alexander Kanavin
2015-09-03 15:34 ` [PATCH 04/12] gnome-icon-theme: remove the recipe Alexander Kanavin
2015-09-03 16:08   ` Burton, Ross
2015-09-04 11:56     ` Jussi Kukkonen
2015-09-04 12:12       ` Alexander Kanavin
2015-09-04 13:32         ` Burton, Ross
2015-09-03 21:28   ` Khem Raj
2015-09-04 12:14     ` Alexander Kanavin
2015-09-04 14:16       ` Khem Raj
2015-09-07  9:37         ` Alexander Kanavin
2015-09-07 15:14           ` Martin Jansa
2015-09-18 17:30             ` World builds HW Was: " Martin Jansa
2015-09-18 17:38               ` Gary Thomas
2015-09-18 17:52                 ` Martin Jansa
2015-09-18 17:56               ` Tom King
2015-10-13 20:43                 ` Randy MacLeod
2015-10-14 13:01                   ` Martin Jansa [this message]
2015-09-03 15:34 ` [PATCH 05/12] libunique: " Alexander Kanavin
2015-09-03 15:34 ` [PATCH 06/12] mkelfimage: add RECIPE_NO_UPDATE_REASON Alexander Kanavin
2015-09-03 15:34 ` [PATCH 07/12] python-async: update to 0.6.2 Alexander Kanavin
2015-09-03 15:34 ` [PATCH 08/12] python-smmap: update to 0.9.0 Alexander Kanavin
2015-09-03 15:34 ` [PATCH 09/12] remake: update to 4.1+dbg-1.1 Alexander Kanavin
2015-09-03 15:34 ` [PATCH 10/12] uclibc: update PV to 0.9.33.2 to match latest upstream release Alexander Kanavin
2015-09-03 20:14   ` Khem Raj
2015-09-04 13:00     ` Alexander Kanavin
2015-09-03 15:34 ` [PATCH 11/12] vte: add RECIPE_NO_UPDATE_REASON Alexander Kanavin
2015-09-03 15:34 ` [PATCH 12/12] package_regex.inc: various updates to improve RRS accuracy Alexander Kanavin

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=20151014130100.GB22448@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.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