1 |
On Tue, 27 Apr 2021 20:53:11 +0000, Alan Mackenzie wrote: |
2 |
|
3 |
> Help! What am I supposed to do? I've got 16 Gb RAM (I'm _not_ going to |
4 |
> use the word "only" here), and wondering just how big a chunk a ram disk |
5 |
> can take out of that before the machine siezes up altogether. But if I |
6 |
> increase the ram disk to 15 Gb, even assuming it'd work, it's only going |
7 |
> to be a small number of releases before the clever people at rust |
8 |
> increase their bloat even more. |
9 |
|
10 |
Setting the RAM disk so high will mean you don't have enough memory for |
11 |
the compilation, which will start swapping and everything will grind to a |
12 |
near halt. |
13 |
|
14 |
> I know I could plump for the -bin package. Maybe I should. But before |
15 |
> I do that, is it possible to redirect this one ebuild away from |
16 |
> /var/tmp/portage (my ram disk) without disturbing the other builds? If |
17 |
> so, how would I do this (or where should I look for documentation)? |
18 |
|
19 |
Lookup package.env on the wiki. I use rust-bin now, so this isn't an |
20 |
issue for me, but my laptop has only 8GB and this is how I have it set |
21 |
for chromium: |
22 |
|
23 |
% cat /etc/portage/env/disk-tmpdir.conf |
24 |
PORTAGE_TMPDIR="/mnt/scratch" |
25 |
|
26 |
% cat /etc/portage/package.env/chromium |
27 |
www-client/chromium disk-tmpdir.conf |
28 |
|
29 |
I do similar for libreoffice and a couple of other heavyweights. |
30 |
|
31 |
Another option, to be used instead of or as well as this would be distcc. |
32 |
Once again, you can use package.env to apply this to selected packages: |
33 |
|
34 |
% cat /etc/portage/env/distcc.conf |
35 |
FEATURES="distcc buildpkg distlocks" |
36 |
MAKEOPTS="-j36 -l4" |
37 |
CFLAGS="-march=broadwell -O2 -pipe" |
38 |
CXXFLAGS="${CFLAGS}" |
39 |
|
40 |
|
41 |
-- |
42 |
Neil Bothwick |
43 |
|
44 |
I'm firm. You're obstinate. He's a pigheaded fool. |