| 1 |
thelma@×××××××××××.com wrote: |
| 2 |
> On 09/05/2015 08:30 AM, Dale wrote: |
| 3 |
> [snip] |
| 4 |
>> |
| 5 |
>> Well, you can leave that in fstab for when you can use it. This is my |
| 6 |
>> understanding. Putting portage's work directory on tmpfs speeds up the |
| 7 |
>> compile because it is done in memory instead of a hard drive. Thing is, |
| 8 |
>> there may be times when some packages don't have enough space to |
| 9 |
>> compile, you run out of tmpfs basically. One example, libreoffice which |
| 10 |
>> uses a lot. I've also found that Firefox also uses a lot of space too. |
| 11 |
>> Of course, I have enough memory at the moment for both to compile. You |
| 12 |
>> may not tho. |
| 13 |
>> |
| 14 |
>> When you don't have enough for say Libreoffice to compile on tmpfs, you |
| 15 |
>> then set a exception for that package. That is where notmpfs comes in. |
| 16 |
>> That allows you to use tmpfs for all the other packages but puts it back |
| 17 |
>> on spinning rust for that package, and any other package you set it for |
| 18 |
>> such as Firefox. |
| 19 |
>> |
| 20 |
>> So, if you have the memory even for large packages like Libreoffice, |
| 21 |
>> just remove the notmpfs part and leave fstab like it was. Basically, |
| 22 |
>> ignore that part of the wiki since you don't need to set that. If you |
| 23 |
>> have say 6GBs of ram, you would need that line in fstab AND the part |
| 24 |
>> about notmpfs. You would not be able to compile Libreoffice with that |
| 25 |
>> small amount of ram and even Firefox may not either. |
| 26 |
>> |
| 27 |
>> Does that clear up the muddy waters any or am I making it worse? Maybe |
| 28 |
>> the better question would be, how much memory does your rig have on it? |
| 29 |
>> Then folks can advise on where to go based on that. ;-) |
| 30 |
>> |
| 31 |
>> Dale |
| 32 |
> Thanks Dale for explanation. |
| 33 |
> I have 8GB RAM and with fstab: |
| 34 |
> tmpfs /var/tmp/portage tmpfs defaults 0 0 |
| 35 |
> |
| 36 |
> it creates 3.9Gb ram disk but that is not enough for firefox I think my default setup was OK with: |
| 37 |
> /etc/portage/package.env |
| 38 |
> /etc/portage/env/notmpfs.conf |
| 39 |
> |
| 40 |
> Thelma |
| 41 |
> |
| 42 |
> |
| 43 |
|
| 44 |
|
| 45 |
What I would do, use tmpfs for everything you can and set up a exception |
| 46 |
for Firefox and anything else that requires a lot of space to compile. |
| 47 |
Basically, follow this part of the wiki for those exceptions like Firefox. |
| 48 |
|
| 49 |
https://wiki.gentoo.org/wiki/Portage_TMPDIR_on_tmpfs#Per-Package_Choices_at_Compile_Time |
| 50 |
|
| 51 |
|
| 52 |
That should give you the best of both worlds. You can use tmpfs to get |
| 53 |
some speed up on smaller packages and use spinning rust for the larger |
| 54 |
packages. Also, you don't have to do all this by hand when you get |
| 55 |
ready to upgrade those since you can tell portage what exceptions you |
| 56 |
need and it will do it for you. I seem to recall when this first |
| 57 |
started a few years ago, a person would have to notice that something |
| 58 |
big was going to be updated and disable tmpfs by hand so to speak and |
| 59 |
then re-enable it afterwards. Having a way to tell portage what to do |
| 60 |
is much easier and less prone to forgetfulness. |
| 61 |
|
| 62 |
You may want to see if Alan agrees with this advice. I've had 16GBs on |
| 63 |
this rig ever since it was built. I love when stuff is on sale. lol |
| 64 |
|
| 65 |
Dale |
| 66 |
|
| 67 |
:-) :-) |
Archives