| 1 |
Nikos Chantziaras wrote: |
| 2 |
> On 08/02/18 21:17, Dale wrote: |
| 3 |
>> I have 16GBs of memory here and have /var/tmp/portage/ on tmpfs, no |
| 4 |
>> ccache. With the growing size of packages, I've had to put several on |
| 5 |
>> regular spinning rust to make sure enough space is available. This is |
| 6 |
>> my list, so far. |
| 7 |
>> |
| 8 |
>> www-client/firefox |
| 9 |
>> www-client/seamonkey |
| 10 |
>> app-office/libreoffice |
| 11 |
>> sys-devel/gcc |
| 12 |
>> dev-qt/qtwebengine |
| 13 |
>> dev-qt/qtwebkit |
| 14 |
> |
| 15 |
> I'm on 16GB as well, with a 9GB /var/tmp/portage tmpfs, and all of the |
| 16 |
> above build fine. No need to build them on disk. |
| 17 |
> |
| 18 |
> Note that tmpfs does not consume any memory if there's no files in it! |
| 19 |
> So you can make your tmpfs larger. Here, 9GB is enough to build the |
| 20 |
> above. However, that's of course for when not using --jobs for |
| 21 |
> emering. Just regular -jN in MAKEOPTS. |
| 22 |
> |
| 23 |
> |
| 24 |
> . |
| 25 |
> |
| 26 |
|
| 27 |
What I run into a lot, Seamonkey and Firefox has a update at the same |
| 28 |
time. Since they are both fairly large, they end up compiling at the |
| 29 |
same time which makes me run short and it fails when it runs out of |
| 30 |
space. So, I just do them on disk and don't worry about it. That said, |
| 31 |
those packages would likely benefit from being done on tmpfs. |
| 32 |
|
| 33 |
As it is right now, I usually have Seamonkey, multiple profiles of |
| 34 |
Firefox running and other programs as well. Those can easily consume |
| 35 |
half of my memory. While tmpfs doesn't "use" anything when it is not in |
| 36 |
use, the other stuff does crowd tmpfs. |
| 37 |
|
| 38 |
I'm hoping to upgrade to 32GBs of ram at some point. I could use it for |
| 39 |
sure. |
| 40 |
|
| 41 |
Dale |
| 42 |
|
| 43 |
:-) :-) |
Archives