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