From owner-freebsd-ports@FreeBSD.ORG Mon Jan 19 19:46:07 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94BED6CD for ; Mon, 19 Jan 2015 19:46:07 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 27980DEE for ; Mon, 19 Jan 2015 19:46:06 +0000 (UTC) Received: from [192.168.0.100] ([87.139.233.65]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0LnkiR-1XWmFK3X95-00huiH; Mon, 19 Jan 2015 20:46:02 +0100 Message-ID: <54BD5EF8.4010201@gmx.de> Date: Mon, 19 Jan 2015 20:46:00 +0100 From: olli hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Kurt Jaeger Subject: Re: Poudriere Timeout References: <201501190145.t0J1jKvg006268@slippy.cwsent.com> <54BCF7C9.7090502@toco-domains.de> <20150119154822.GX44537@home.opsec.eu> <54BD3203.5050809@toco-domains.de> <20150119191834.GH83169@home.opsec.eu> In-Reply-To: <20150119191834.GH83169@home.opsec.eu> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:vCY1nb6dmY3wylzF50+SAZFDH+q+o1q7EbewG1MtF1jHsG4yyjn z601ewGVanoQm0IkIiyownCVlk82QShQ/Rxou/Xxdoqhz4aV7gUBzVZZmb68BB1hg4+noDZ +cbGbBQlP4u/hPJCcRSwn2m3KbtXc8yDilnWogRH/0lXE4G5dGJoEXCu6U/2NUBVnOhs8tS s3b2wXdmF7+gRI33NFJfA== X-UI-Out-Filterresults: notjunk:1; Cc: freebsd-ports@freebsd.org, Torsten Zuehlsdorff X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2015 19:46:07 -0000 On 2015-01-19 20:18, Kurt Jaeger wrote: > Hi! > >>>> Yes, i have. I've solved this problem by moving the build-jails of >>>> poudriere to an memory disk. This make poudriere no longer io-bund and >>>> incredibly fast. And solve this issue ;) > >>> How did you do this ? I want to try this myself 8-} > >> I've hacked poudriere to run within a jail. > > Aha, the .m mountpoint. My test host has 32 GB, so 20 GB should not be > a problem. > > Testport: www/p5-Selenium-Remote-Driver on 10.1-amd64, 9.3-amd64 and 8.4-i386. > > Results: > > old: 00:05:43 > new: 00:05:11 > > old: 00:01:56 > new: 00:00:12 > > old: 00:02:11 > new: 00:00:14 > > Nice! > Hi Kurt, are you running PD also in a jail? If not PD can be tuned by setting MFSSIZE *or* USE_TMPFS in poudriere.conf. On my system I have good results with 8 concurrent builds and MFSSIZE=6G or 'USE_TMPFS=all'. Fine tuning can be done with an additional SSD (look at `systat -iostat' during a build) poudriere.conf: # When building packages, a memory device can be used to speedup the build. # Only one of MFSSIZE or USE_TMPFS is supported. TMPFS is generally faster # and will expand to the needed amount of RAM. MFS is a bit slower, but is # more mature and can have its memory usage capped. # If set WRKDIRPREFIX will be mdmfs of the given size (mM or gG) #MFSSIZE=4G # Use tmpfs(5) ... # all - Run the entire build in memory, including builder jails. USE_TMPFS=all -- olli