1 |
On Tuesday, 13 October 2020 09:30:00 BST Jude DaShiell wrote: |
2 |
|
3 |
> I'm trying -j1 first. This machine has 50% of its maximum ram capacity |
4 |
> in use and only has 2gb of ram capacity so yes this is a low memory |
5 |
> machine. Why I'm using it at all is since it has available a 3tb hard |
6 |
> drive. As long as /tmp directories under the $HOME directory structure |
7 |
> have better system protection than /tmpfs and /var/tmp if the -j1 build |
8 |
> fails I'll try pointing the memory to a safer place. I need to buy some |
9 |
> decent sized ssd drives since that way I can do this on my new machine |
10 |
> with 14GB of ram. |
11 |
|
12 |
OK, your RAM is not enough to build most large packages today. I'm thinking |
13 |
rust, chromium, gcc, firefox, libreoffice, as examples. Most of these will |
14 |
refuse to emerge right at the start as they check for adequate /var/tmp space. |
15 |
In any case, the solution for low RAM PCs is to set up adequate space on your |
16 |
disk for those packages only. Also to increase your swap, or add a swapfile |
17 |
just for these larger packages. |
18 |
|
19 |
Have a read at 'Example 2' here: |
20 |
|
21 |
https://wiki.gentoo.org/wiki//etc/portage/package.env |
22 |
|
23 |
If your / fs partition has inadequate free space, you can set up /var/tmp/ |
24 |
notmpfs to a different partition as long as you remember to mount it with |
25 |
'mount -o exec' and activate any swapfile(s) in advance. |
26 |
|
27 |
If you only set up more swap and leave PORTAGE_TMPDIR on RAM, the swapping |
28 |
from your RAM to disk will inevitably incur I/O bottleneck conditions and will |
29 |
start thrashing the disk, which could slow everything down to a crawl, |
30 |
potentially for days. Therefore, it is worth switching to BFQ scheduler when |
31 |
heavy swappage is expected: |
32 |
|
33 |
# echo bfq > /sys/block/sda/queue/scheduler |
34 |
|
35 |
where sda is the disk on which the swapfile or partition is set. |