On Wed, 28 Apr 2021 11:12:33 +0000, Alan Mackenzie wrote: > > I use rust-bin now, so this isn't an issue for me, but my laptop has > > only 8GB and this is how I have it set for chromium: > > > % cat /etc/portage/env/disk-tmpdir.conf > > PORTAGE_TMPDIR="/mnt/scratch" > > > % cat /etc/portage/package.env/chromium > > www-client/chromium disk-tmpdir.conf > > > I do similar for libreoffice and a couple of other heavyweights. > > With a like setup, building rust took ~45 minutes. This is about the > same as it took on the ram disk before giving up. So, I'm not losing a > lot, if anything, by using /home/portage (On mirrored nvme SSDs).
There have been several tests posted over the years that show that using a tmpfs for TMPDIR doesn't give as much of a gain as you would expect. With NVMe drives, the difference is likely to be even smaller. > > > Another option, to be used instead of or as well as this would be > > distcc. Once again, you can use package.env to apply this to selected > > packages: > > That's for building on a different (more powerful) machine, isn't it? I > don't actually have a more powerful machine. ;-) A different machine, not necessarily more powerful. The point is that you are splitting the workload between the different computers. My desktop is currently emerging chromium, and is sending some of the work to my MythTV backend, which is actually the old desktop machine it replaced. -- Neil Bothwick Time for a diet! -- [NO FLABBIER].
pgp8p56cxXq1F.pgp
Description: OpenPGP digital signature
