Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mx1.pokylinux.org (Postfix) with ESMTP id 1C0564C80050 for ; Tue, 21 Dec 2010 11:31:34 -0600 (CST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 21 Dec 2010 09:31:23 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.60,208,1291622400"; d="scan'208";a="638888804" Received: from unknown (HELO qhe2-db.sh.intel.com) ([10.239.13.38]) by fmsmga002.fm.intel.com with ESMTP; 21 Dec 2010 09:31:22 -0800 Received: from qhe2 by qhe2-db.sh.intel.com with local (Exim 4.71) (envelope-from ) id 1PV5xg-0001d4-JT for poky@yoctoproject.org; Wed, 22 Dec 2010 01:25:20 +0800 Date: Wed, 22 Dec 2010 01:25:20 +0800 From: Qing He To: "poky@yoctoproject.org" Message-ID: <20101221172520.GA29120@qhe2-db> References: MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: [RFC 0/4] socketed based data connection X-BeenThere: poky@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Poky build system developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2010 17:31:35 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, 2010-12-22 at 00:49 +0800, He, Qing wrote: > This patch set enables remote data access in the exec'd task process. It's intended to be proof of concept to an alternative approach to work around the slowness introduced by exec bitbake-runtask. The patch is still WIP. http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=qhe/datasock Thanks, Qing > > Some test data: > I've conducted a poky-image-minimal build on two different machines > with and without the patch, the result are as follow: > > 2 core weybridge: worker count=4, make -j4 > without patch > real: 161min > user: 237min > sys: 56min > with patch > real: 138min > user: 196min > sys: 45min > 4 core nehalem: worker count=4, make -j4 > without patch > real: 88min > user: 218min > sys: 37min > with patch > real: 83min > user: 160min > sys: 29min > > the user+sys has an improvement of around 20%~30%, however the > real runtime improvement is less significant. It's probably > because of the thread workload unbalance on multicore, or in another > word, some CPUs are not fully loaded during the build. e.g. when > do_rootfs_rpm is run, there is probably no other tasks running. > > Haven't done any test against single thread running, but it should > have a much more considerable impact. > > > Known problems: > 1. fetcher is not working at the moment, maybe bitbake needs an explicit > InheritFromOS(), but that produces some inconsistency in PATH in my previous > run > 2. do_rootfs_rpm has some problem in the first run > > > Next step and possible future usage: > 1. organize remote data to a separate class > 2. although we have reverted to fork for task running, a remote data mechanism > would work for a more separate build (e.g. distributed build) > 3. the added code in bitbake-runtask is to run necessary initializations for a > working environment, this is part of cooker. The current cooker seems too heavy > and may be broken down into several pieces according to functionalitiies > > Thanks, > Qing > > > Pull URL: git://git.pokylinux.org/poky-contrib.git > Branch: qhe/datasock > Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=qhe/datasock > > Thanks, > Qing He > --- > > > Qing He (4): > python method fix > sstate.bbclass: workaround > data_smart: remote data > socket based worker data > > bitbake/bin/bitbake-runtask | 80 +++++++++++++++++++++++++++++++++-------- > bitbake/lib/bb/data_smart.py | 25 ++++++++++++- > bitbake/lib/bb/methodpool.py | 6 +++ > bitbake/lib/bb/parse/ast.py | 2 +- > bitbake/lib/bb/runqueue.py | 68 ++++++++++++++++++++++++++++++++---- > meta/classes/sstate.bbclass | 2 +- > 6 files changed, 157 insertions(+), 26 deletions(-) >