| 1 |
On Tuesday 07 July 2009 15:36:23 Frank Peters wrote: |
| 2 |
> After reading through the thread on this list about the benefits |
| 3 |
> of mounting PORTAGE_TMPDIR as tmpfs, I decided that I will be doing |
| 4 |
> this mount from now on. My total RAM is 4G, but since I only "emerge |
| 5 |
> world" about once per week, I can easily set aside temporarily 2G or more |
| 6 |
> for this purpose. |
| 7 |
> |
| 8 |
> However, after doing some more reading, I find that some people recommend |
| 9 |
> mounting tmpfs using the option nr_inodes=1M, while others just accept |
| 10 |
> the default value for nr_inodes. |
| 11 |
> |
| 12 |
> To me, setting maximum inodes to 1M seems a bit high. Can emerge |
| 13 |
> actually generate that many temporary files? Would it be safer and also |
| 14 |
> avoid swapping to set nr_inodes=1M or is the default good enough?. |
| 15 |
|
| 16 |
This is my fstab line: |
| 17 |
|
| 18 |
tmpfs /tmp tmpfs nodev,nosuid,size=6g 0 0 |
| 19 |
|
| 20 |
I have 4GB RAM. If /tmp filled up too much I'd find the machine swapping, |
| 21 |
but I've never noticed it doing so. I've also watched top while doing some |
| 22 |
large jobs, and it's never shown more than a little swap space used and |
| 23 |
I've never caught it doing any swap transfers. |
| 24 |
|
| 25 |
HTH. |
| 26 |
|
| 27 |
-- |
| 28 |
Rgds |
| 29 |
Peter |
Archives