| 1 |
On 19/06/2014 12:56, Rich Freeman wrote: |
| 2 |
> On Thu, Jun 19, 2014 at 7:44 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 3 |
>> On Thu, 19 Jun 2014 16:40:08 +0800, Amankwah wrote: |
| 4 |
>> |
| 5 |
>>> Maybe the only solution is that move the portage tree to HDD?? |
| 6 |
>> |
| 7 |
>> Or tmpfs if you rarely reboot or have a fast enough connection to your |
| 8 |
>> preferred portage mirror. |
| 9 |
> |
| 10 |
> There has been a proposal to move it to squashfs, which might |
| 11 |
> potentially also help. |
| 12 |
> |
| 13 |
> The portage tree is 700M uncompressed, which seems like a bit much to |
| 14 |
> just leave in RAM all the time. |
| 15 |
|
| 16 |
The tree will not necessarily be left in RAM all of the time. Pages |
| 17 |
allocated by tmpfs reside in pagecache. Given sufficient pressure, they |
| 18 |
may be migrated to swap. Even then, zswap [1] could be used so as to |
| 19 |
reduce write amplification. I like Neil's suggestion, assuming that the |
| 20 |
need to reboot is infrequent. |
| 21 |
|
| 22 |
--Kerin |
| 23 |
|
| 24 |
[1] https://www.kernel.org/doc/Documentation/vm/zswap.txt |
Archives