Return-Path: Delivered-To: apmail-builds-archive@minotaur.apache.org Received: (qmail 65058 invoked from network); 28 Oct 2009 15:47:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Oct 2009 15:47:49 -0000 Received: (qmail 64023 invoked by uid 500); 28 Oct 2009 15:47:49 -0000 Delivered-To: apmail-builds-archive@apache.org Received: (qmail 63974 invoked by uid 500); 28 Oct 2009 15:47:49 -0000 Mailing-List: contact builds-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: builds@apache.org Delivered-To: mailing list builds@apache.org Received: (qmail 63940 invoked by uid 99); 28 Oct 2009 15:47:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Oct 2009 15:47:49 +0000 X-ASF-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of t.p.ellison@gmail.com designates 216.239.58.188 as permitted sender) Received: from [216.239.58.188] (HELO gv-out-0910.google.com) (216.239.58.188) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Oct 2009 15:47:47 +0000 Received: by gv-out-0910.google.com with SMTP id o2so130041gve.26 for ; Wed, 28 Oct 2009 08:47:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=FKRzOJOPR7+TwVXozekHgkTulv75beis1YBH9aFdc5g=; b=K7G1u1Czj7UusjPSYgmmFnIpN8b9qUE6sRLM3El5c4SiuB2STx1Jzo1oT8B5W6aXsc xi2T3bptAx83LLTkT/t2d5sFgmQvaz5tAH27dq5VPrpn5M0eD+iNnsZVsMvzmrRzVO1Y jaK1eVdF5Butfr7pRFN/gsWTGXyqwMduMHwR4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=kb/3L6dqNjVMlgwCyE7C/0ox64zn+6ZtltSHPBWF2aORmBdubU4SGmbJnwdBHh6ERu E1Q72G0aplHMlw7IdxysR2QtYVNCuiFh+6i5WCV5XDP2k7UbHqGpchF06noYxrrIm6I6 Lmwcayzi35CdrxEVodGggiv0kX6WuL5Pu/dPQ= Received: by 10.87.40.9 with SMTP id s9mr150584fgj.11.1256744845718; Wed, 28 Oct 2009 08:47:25 -0700 (PDT) Received: from ?9.20.183.75? (blueice2n1.uk.ibm.com [195.212.29.75]) by mx.google.com with ESMTPS id e11sm2493291fga.2.2009.10.28.08.47.24 (version=SSLv3 cipher=RC4-MD5); Wed, 28 Oct 2009 08:47:24 -0700 (PDT) Message-ID: <4AE86789.9000100@apache.org> Date: Wed, 28 Oct 2009 15:47:21 +0000 From: Tim Ellison User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: builds@apache.org Subject: Re: Hudson machine utilization References: <4AE859A1.3070808@gmail.com> <6c399e450910280813j1b305de7hcfd0c2228cac97f7@mail.gmail.com> In-Reply-To: <6c399e450910280813j1b305de7hcfd0c2228cac97f7@mail.gmail.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 28/Oct/2009 15:13, Justin Mason wrote: > Well, we could move more load from hudson.zones to minerva first: > > http://hudson.zones.apache.org/hudson/computer/%28master%29/load-statistics > http://hudson.zones.apache.org/hudson/computer/minerva.apache.org%20%28Ubuntu%29/load-statistics > > (wow, those are good graphs!) Why do you say to do that first? At least there are times when Minerva is using both its executors. However, it looks like we could get by with half the current number of the Hadoop labeled machines without impacting anything. http://hudson.zones.apache.org/hudson/label/Hadoop/load-statistics?type=hour > We certainly should embark on a program of persuading projects to > schedule their jobs on both Linux and Solaris, though, to do that.... Maybe we can just define a useful set of labels to sets of nodes and encourage people to tie builds to them rather than specific machines. Regards, Tim > On Wed, Oct 28, 2009 at 14:48, Tim Ellison wrote: >> Just looking at the Hudson machine utilization at the moment. There are >> a number of jobs that are tied to particular machines in the queue, and >> a number of (hadoop-labeled) machines that are committed to tied jobs only. >> >> I realize that the machines are courteously donated etc, but is the >> capacity being used effectively [1]? >> >> In particular, would the Hadoop jobs be impacted if we reclassified an >> existing slave as general usage, and more jobs as scheduable anywhere? >> >> [1] e.g. >> http://hudson.zones.apache.org/hudson/computer/hadoop1%20%28Ubuntu%29/load-statistics?type=hour >> >> Regards, >> Tim >> >> > > >