| 1 |
On Tue, 21 Jan 2014 18:03:08 +0100, Jarry wrote: |
| 2 |
|
| 3 |
> I would like to use tmpfs for all the package-compilation |
| 4 |
> to spare my SSD from too many writing-cycles, but I can not |
| 5 |
> guess how much do I need. I'm rather limited with RAM, |
| 6 |
> if I use more than 512MB for /var/tmp/portage, my server |
| 7 |
> lowers buffers/cache to nearly zero and starts swapping... |
| 8 |
|
| 9 |
Then don't use more than 512MB, I certainly wouldn't use less for the |
| 10 |
packages you mention. |
| 11 |
|
| 12 |
> So what do your think? Would it be enought to have 512MB |
| 13 |
> for packages like GCC, Apache, MySQL, Sendmail, Bind? |
| 14 |
> These are the biggest, rest are much smaller... |
| 15 |
|
| 16 |
Packages that need a particularly large amount of space usually check its |
| 17 |
availability at the start of the emerge process. There's nothing to stop |
| 18 |
you using tmpfs for the default PORTAGE_TMPDIR and resetting it to |
| 19 |
somewhere on your drive for particularly large packages, using |
| 20 |
package.env |
| 21 |
|
| 22 |
Put "cat/pkg tmpondisk.conf" in /etc/portage/package.env and |
| 23 |
"PORTAGE_TMPDIR=/a/disk/dir" in /etc/portage/env/tmpondisk.conf |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Neil Bothwick |
| 28 |
|
| 29 |
Engineers do it with less resistance. |
Archives