From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id CD9BC1384B4 for ; Tue, 10 Nov 2015 19:22:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 917AF21C068; Tue, 10 Nov 2015 19:21:47 +0000 (UTC) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 95A3F21C064 for ; Tue, 10 Nov 2015 19:21:46 +0000 (UTC) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 16B4521732 for ; Tue, 10 Nov 2015 14:21:46 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 10 Nov 2015 14:21:46 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=cfxneXez9+b0Enh bHi0DxGKOMXc=; b=pyLMAcagNlKxs3wQh8xUKKWqEkGhTd1xcXx1nxYwThWo8DT YweHnEg3ks2DfSYwW+orOX6bT2oSr9b3yw1b2YvIc8fMqpfmRPSzB9Dfq2uVFO1t /rCEVcfDd55ffo/DnG4/9LWRQ1c54zCmuKpknfWVFu/lVTZTtJmfLtk5UADo= X-Sasl-enc: CT7QZFXyAQQQ85BT1Qz6veCC0I7CCs70GpR/N/fsfFNs 1447183305 Received: from [192.168.0.40] (c-68-42-214-119.hsd1.mi.comcast.net [68.42.214.119]) by mail.messagingengine.com (Postfix) with ESMTPA id C0A4D6801AD for ; Tue, 10 Nov 2015 14:21:45 -0500 (EST) Subject: Re: [gentoo-user] Better CPU for compiling with gcc To: gentoo-user@lists.gentoo.org References: <56422D9C.6060001@gmail.com> <201511101817.35016.michaelkintzios@gmail.com> <56423958.2030802@gmail.com> <56423DB7.4030605@gmail.com> <5642406E.2080808@gmail.com> From: Alec Ten Harmsel Message-ID: <564243D2.6030107@alectenharmsel.com> Date: Tue, 10 Nov 2015 14:21:54 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <5642406E.2080808@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 14ff3c3b-7cc4-47d9-98a2-80cbb6615196 X-Archives-Hash: d1371bad3eef88cf25dda51b2c580175 On 2015-11-10 14:07, Stanislav Nikolov wrote: > > On 11/10/2015 08:55 PM, Alan McKinnon wrote: >> On 10/11/2015 20:37, Stanislav Nikolov wrote: >>> On 11/10/2015 08:17 PM, Mick wrote: >>>> On Tuesday 10 Nov 2015 17:47:08 Stanislav Nikolov wrote: >>>>> Dear Gentoo users, >>>>> I'm building a new PC. I have a budget of ~$550-$650. >>>>> >>>>> >>>>> >>>>> The most expensive Intel CPU is the skylake i7-6700k. >>>>> >>>>> Thanks >>>> >> >> I can't help but think you are approaching this from the wrong perspective. >> >> Why exactly are you using compile times as your sole criterion? Are you >> building a compile farm for Ubuntu? Running continuous integration tests >> for LibreOffice [on a $600 budget in a cardboard box :-) ]? >> >> Or do you want emerge world to get it over with quicker? >> >> If the latter, you better rethink your priorities. In computing terms, >> compilation is a rare event; launching apps is a common event; and >> writing to the disk happens all the time. Optimize for the common case. In addition, upgrades are something that can be done overnight, or really any time you are not using the machine. >> >> A CPU never works in isolation, it is always part of a much larger >> system, like disks, RAM and all possible kinds of I/O. The best CPU on >> the market plugged into a POS motherboard will perform on emerge world >> like a piece of shit - it will follow the weakest link. This; I have an i7-3930K, which has 6 physical cores at 3.8GHz. I also have 32GB of RAM and an SSD. There was a large speedup[1] moving portage's workdir from SSD to tmpfs. Compiling is a really balanced workload, stressing the disk (multiple small reads), memory, and CPU. For fast compilation, emphasize RAM first (compile in tmpfs if possible), then CPU, then disk. Like Alan said, though, you should really optimize for the average case on not worry about the speed of compiling stuff. Alec 1. It was a long time ago so I don't remember the exact numbers, but my firefox compiling time went from ~15 minutes to ~10 minutes after switching from SSD to tmpfs for portage's workdir.