From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from muon.cran.org.uk (muon.bluestop.org [IPv6:2605:7700:0:8:1:0:4a32:3323]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 667AE82171 for ; Thu, 23 Feb 2017 11:10:05 -0800 (PST) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 96F45F719; Thu, 23 Feb 2017 19:10:04 +0000 (UTC) Received: from muon.cran.org.uk ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id TFXyPmve5g6K; Thu, 23 Feb 2017 19:10:02 +0000 (UTC) Received: from [192.168.1.28] (c-73-20-20-155.hsd1.ut.comcast.net [73.20.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Thu, 23 Feb 2017 19:10:02 +0000 (UTC) To: "Brian J. Johnson" , "Wei, David" , "Richardson, Brian" , "Gao, Liming" , "edk2-devel@lists.01.org" References: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6E27B3@shsmsx102.ccr.corp.intel.com> <95a8d930-6bb2-e666-1957-8d78a25efd10@bluestop.org> <80AC2BAA3152784F98F581129E5CF5AF6655EC20@ORSMSX114.amr.corp.intel.com> <2d7462e9-de6c-67b2-ffd7-a3fa194ce06b@bluestop.org> <80AC2BAA3152784F98F581129E5CF5AF6655F06F@ORSMSX114.amr.corp.intel.com> <89954A0B46707A448411A627AD4EEE3468EFDFFF@SHSMSX101.ccr.corp.intel.com> Cc: "Lu, ShifeiX A" , "Zimmer, Vincent" , Andrew Fish From: Rebecca Cran Message-ID: Date: Thu, 23 Feb 2017 12:10:03 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: Subject: Re: Improvements to build system etc. for edk2-platforms devel-MinnowBoard3? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 19:10:05 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 2/23/2017 11:53 AM, Brian J. Johnson wrote: > Sorry if I'm bikeshedding... NUMBER_OF_PROCESSORS isn't a good > default for those of us who build on servers with hundreds of threads > available. The OS, disks, and build.exe/build.py become bottlenecks. > Maybe we could put a cap (say, 20) on the default thread limit, so it > uses NUMBER_OF_PROCESSORS or 20 threads, whichever is less. > > Or just set a small, fixed number of threads by default and document > better how to change it, as others suggested. Good point. I think the best approach will be to have a --setup parameter which configures defaults in Conf/target.txt, after which users can change MAX_CONCURRENT_THREAD_NUMBER - instead of the current method which involves figuring out which of files ends up running build.exe with '-n '. -- Rebecca