cov...@ccs.covici.com wrote: > Neil Bothwick <n...@digimed.co.uk> wrote: > >> On Wed, 17 Dec 2014 20:59:23 -0500, cov...@ccs.covici.com wrote: >> >>> Mine takes more than an hour, I don't use tmpfs for /var/tmp/portage >>> because sometimes I need many gigs even more than memory for certain >>> packages. But Linux is pretty good at disk caching, so I wonder if that >>> is it? >> You can change PORTAGE_TMPDIR per-package. I have it on a tmpfs and then >> change it for packages like LO. >> >> % cat /etc/portage/package.env/libreoffice >> app-office/libreoffice disk-tmpdir.conf >> >> % cat /etc/portage/env/disk-tmpdir.conf >> PORTAGE_TMPDIR="/mnt/scratch" > That is interesting, but firefox requires 8g I think of temp space, the > very package which takes so long. I have 16g of memory, but I wonder if > my whole system would start to crawl. > >
I have 16Gbs here and I have portage on tmpfs. Only once has it ran out of room and it was slow as expected. It was working on seamonkey, firefox and LOo all at the same time. Yea, it was memory hungry. It has only did that once during a emerge -e world tho. It's never happened during a normal update. I think setting at least LOo to not use memory would pretty much fix this issue. I plan to work on that at some point. I also plan to work on upgrading to 32Gbs too. Dale :-) :-)
