From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id F281D1382C5 for ; Thu, 8 Feb 2018 21:53:06 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4C96EE0BA6; Thu, 8 Feb 2018 21:53:00 +0000 (UTC) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CD8AEE0B7D for ; Thu, 8 Feb 2018 21:52:59 +0000 (UTC) Received: by mail-io0-x232.google.com with SMTP id b198so7432102iof.6 for ; Thu, 08 Feb 2018 13:52:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=3UWLkylcrJh1N3ObqzbBWrsPX7v/LbEQip3qHgzWvzg=; b=O8lbSKV+Hnrgcnqm0lji2AKMABHWx1bmq7+qQvZTe7n4PcHfaznYSUzsPSiHCEDn/4 buLXHVm4y/lMTqRy1nce5i3xAI4CrQhe3MRk+wD264EP8EV6bpZ4ItNKuKEmNM3BXlR4 Q/3vyZiV6xhuuCSc6pvw56F2wqKch49gswUQkGth6aqNPyTaGFK6T/T7/2dgUoIQQg6h elsg19dzEcssieHVMWvQJRr74Vh067b8bsSLnypqQTl2P4dneZTWyDLHWI14LmlLBgHN xV8F4vOIXT/T/qJDXtJNTCxmgsfYfRolQOTBoGOj/62MJbWADXTyBhvJvYobKn/8mITe 53jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=3UWLkylcrJh1N3ObqzbBWrsPX7v/LbEQip3qHgzWvzg=; b=F04U3OQxeYYrf67o01t8ZMcw4jaECnTbgGyuqBPwsJXvXk14IJ2kucJQBr8UPhgA1q yl22rE9wy/k8H2LBTyHU1fg+JKWpDMuC8kIEbiA90SaPfQ3fD/TGk1Ib1t1kq8e5cAWd MyhQQKg/dzeCqksoaq34zeRtsCf0KECqiwKXWxP3Vty3w48xrygcEcE+QxNk4G8/WiPs +yVPpfDcNaDwT7yBCDGa7l4DwBjulQTjf1ViNNOy1sik/k66+7Ngoxt32nVBpE3kvHg0 kctaS0WISCoXIkXSyxQhk/y+BwfsKvmYarExajgK/4AJDOvgWgGZVDtzg3bbGndMFXZE 9sPA== X-Gm-Message-State: APf1xPDgU+rIzqob1zcAPjqCOvNdAcRE9NqOjPv33IGNkYoFb+KTyEVY smQzuq6+Zoe4qbcqVelPr97Er7vr+uIdRpu7fxT7kQ== X-Google-Smtp-Source: AH8x2241855DaWkm1Mw9aCk3TLeRvBK6ACEu6r1wIVVAvkLsVKmsCyC/13CkDOfTTZ82M9I86HFMlV2nZ9JNfirVObc= X-Received: by 10.107.16.8 with SMTP id y8mr637058ioi.213.1518126778955; Thu, 08 Feb 2018 13:52:58 -0800 (PST) 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 Received: by 10.107.173.227 with HTTP; Thu, 8 Feb 2018 13:52:58 -0800 (PST) In-Reply-To: References: From: gevisz Date: Thu, 8 Feb 2018 23:52:58 +0200 Message-ID: Subject: Re: [gentoo-user] Re: /var/tmp on tmpfs To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 036d9014-1386-4695-88ba-e2fa3ae0a862 X-Archives-Hash: cc6869e881da70e6ee58cd1a96667c2c 2018-02-08 20:13 GMT+02:00 Rich Freeman : > On 08/02/18 19:11, gevisz wrote: >> >> I never used tmpfs for portage TMPDIR before and now decided to give it a >> try. >> >> I have 8GB of RAM and 12GB of swap on a separate partition. >> >> Do I correctly understood >> https://wiki.gentoo.org/wiki/Portage_TMPDIR_on_tmpfs >> that I can safely set in the fstab the size of my tmpfs to 12GB so >> that the chromium could be emerged in tmpfs (using the swap) >> without the need to set notmpfs.conf for chromium and the likes. > > You can try it, but for Chromium these days you might find that still > doesn't perform great. I have 16GB of RAM (no swap) and have moved > back to building on SSD for that one package (with ccache to help). > > In an ideal world swap would STILL be better than building on disk, > because it gives the kernel fewer constraints around what gets written > to disk. > Anything written to disk MUST end up on the disk within the dirty > writeback time limit. Anything written to tmpfs doesn't ever have to > end up on disk, and if it is swapped the kernel need not do it in any > particular timeframe. Also, the swapfile doesn't need the same kinds > of integrity features as a filesystem, which probably lowers the cost > of writes somewhat (if nothing else after a reboot there is no need to > run tmpreaper on it). > So, swapping SHOULD still be better than building on disk, because any > object file that doesn't end up being swapped is a saved disk IO, and > the stuff that does get swapped will hopefully get written at a more > opportune time vs forcing the kernel to stop what is doing after 30s > (by default) to make sure that something gets written no matter what > (if it wasn't deleted before then). Thank you for the reply. I probably try a pure tmpfs + swap solution. If it fails some day, I will then add notmpfs exceptions. However, it probably won't be sooner than # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world --exclude chromium fails because of the "--exclude chromium" part :), as I have already compiled the recent vertion of chromium with /var/tmp/portage on the hard disk and it took more than 24 hours on my old AMD Athlon X2 with j2 option. :(