From nobody Tue Dec 13 11:36:16 2022 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NWbzs5F12z4ks3r for ; Tue, 13 Dec 2022 11:36:25 +0000 (UTC) (envelope-from paul@ifdnrg.com) Received: from outbound.ifdnrg.com (outbound.ifdnrg.com [193.200.98.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "outbound.ifdnrg.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NWbzr5tJHz3Hjg for ; Tue, 13 Dec 2022 11:36:24 +0000 (UTC) (envelope-from paul@ifdnrg.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ifdnrg.com header.s=ifdnrg-default header.b=uc+5Vn8A; spf=pass (mx1.freebsd.org: domain of paul@ifdnrg.com designates 193.200.98.22 as permitted sender) smtp.mailfrom=paul@ifdnrg.com; dmarc=pass (policy=quarantine) header.from=ifdnrg.com Received: from [192.168.0.10] (cpc103056-sgyl39-2-0-cust154.18-2.cable.virginm.net [94.173.208.155]) (authenticated bits=0) by outbound.ifdnrg.com (8.17.1/8.16.1) with ESMTPSA id 2BDBaDEn005839 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Tue, 13 Dec 2022 11:36:13 GMT (envelope-from paul@ifdnrg.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ifdnrg.com; s=ifdnrg-default; t=1670931373; bh=J7RP7XWc4+AGIsOD6uyMS+slYOYWHFOMCPpOe9tiwyU=; h=Date:Subject:To:References:From:In-Reply-To; b=uc+5Vn8AKa3jE126FFWikBeSd5BpRUmQMJCSB3Fqd3KtBtQSZmm2Od57fh/XIAcu6 lWjM/TPIYfbkTJj7avoPEJhdjbVwwfyS91JHGemBzad9mHOJr1T7lmzcCN/nB46X0i OUP/BsQTujcV/E1TeZWt8c4TwcjJLq18StZu/GWXARKvuo3E7pIDWIvG3i94ioXEFW t3eaE+8dT3wi6/2ACAfkFxToGTuA9YyUQdh0Gc+MoyHSZaVkEtDF9CIGQuFK5FPAdj vuHtXYOABVSf3euyK5dodJj9EOfz7QDIFCgXEX5cg/57c7bdhvzHoYasC19SIQ1PvB zfJtb3UuTLodA== Content-Type: multipart/alternative; boundary="------------Oix6gEiiay22p8Fx0UhCaG7Z" Message-ID: <0cc38edc-2589-a459-d7dd-61451a145b8c@ifdnrg.com> Date: Tue, 13 Dec 2022 11:36:16 +0000 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Subject: Re: lang/rust is super slow to build To: questions@freebsd.org References: <64a29447-0b4a-eca0-7264-24d9d1afb3a9@tinka.africa> From: paul macdonald In-Reply-To: X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[ifdnrg.com,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:193.200.98.0/24]; R_DKIM_ALLOW(-0.20)[ifdnrg.com:s=ifdnrg-default]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:20860, ipnet:193.200.98.0/23, country:GB]; DKIM_TRACE(0.00)[ifdnrg.com:+]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[paul]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4NWbzr5tJHz3Hjg X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------Oix6gEiiay22p8Fx0UhCaG7Z Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 13/12/2022 03:42, paul beard wrote: > > > On Mon, Dec 12, 2022 at 7:38 PM Mark Tinka wrote: > > > > On 12/12/22 21:27, Pat Maddox wrote: > > > Using poudriere, lang/rust is at 2 hours and counting on my > 10-core i9 > > w/ 128 gigs of RAM. > > > > Does that sound right? It seems extremely slow to me, but this > is my > > first time building it. > > > > How long does it take others to build? What options are you > using, or > > any other suggestions for shortening the time? > > I've found the only way to shorten the time is to install the binary > package. > > It normally takes a couple of hours to build on my systems when I use > the Ports, which I don't mind. I do have some systems that were > not well > configured for space when they were installed, and building Rust on > these consumes all the disk space during the build phase. For > these, I > just upgrade from binary and I'm done with it. Takes all of 2 minutes. > > Mark. > > > I swapped to binary upgrades for this port…it would fill up swap and > die before completing, after hours of work. Never understood why > WORKDIR pointed to my small /tmp partition vs my generous /usr > filesystem. > > -- > I had same issue, and it seems like there's been an llvm/rust/gcc update very often we are now switching to prebuilt for these, but out toolchains are all setup for ports so its not a trivial task. interesting tip re workdir ( although i'd still prefer it not to be churning away for hrs) -- ------------------------- Paul Macdonald (he/him) IFDNRG Ltd Web and video hosting ------------------------- t: 0131 5548070 m: 07970339546 e:paul@ifdnrg.com w:http://www.ifdnrg.com ------------------------- IFDNRG 40 Maritime Street Edinburgh EH6 6SA ---------------------------------------------------- Virtual Servers from £50.00pm High specification Dedicated Servers from £150.00pm ---------------------------------------------------- --------------Oix6gEiiay22p8Fx0UhCaG7Z Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit


On 13/12/2022 03:42, paul beard wrote:


On Mon, Dec 12, 2022 at 7:38 PM Mark Tinka <mark@tinka.africa> wrote:


On 12/12/22 21:27, Pat Maddox wrote:

> Using poudriere, lang/rust is at 2 hours and counting on my 10-core i9
> w/ 128 gigs of RAM.
>
> Does that sound right? It seems extremely slow to me, but this is my
> first time building it.
>
> How long does it take others to build? What options are you using, or
> any other suggestions for shortening the time?

I've found the only way to shorten the time is to install the binary
package.

It normally takes a couple of hours to build on my systems when I use
the Ports, which I don't mind. I do have some systems that were not well
configured for space when they were installed, and building Rust on
these consumes all the disk space during the build phase. For these, I
just upgrade from binary and I'm done with it. Takes all of 2 minutes.

Mark.


I swapped to binary upgrades for this port…it would fill up swap and die before completing, after hours of work. Never understood why WORKDIR pointed to my small /tmp partition vs my generous /usr filesystem. 

--


I had same issue, and it seems like there's been an llvm/rust/gcc update very often

we are now switching to prebuilt for these, but out toolchains are all setup for ports so its not a trivial task.

interesting tip re workdir ( although i'd still prefer it not to be churning away for hrs)


-- 
-------------------------
Paul Macdonald (he/him)
IFDNRG Ltd
Web and video hosting
-------------------------
t: 0131 5548070
m: 07970339546
e: paul@ifdnrg.com
w: http://www.ifdnrg.com
-------------------------
IFDNRG
40 Maritime Street
Edinburgh
EH6 6SA
----------------------------------------------------

Virtual Servers from £50.00pm
High specification Dedicated Servers from £150.00pm

----------------------------------------------------
--------------Oix6gEiiay22p8Fx0UhCaG7Z--