From: Kerin Millar <kerframil@fastmail.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [Gentoo-User] emerge --sync likely to kill SSD?
Date: Thu, 19 Jun 2014 13:16:53 +0100 [thread overview]
Message-ID: <53A2D4B5.3060805@fastmail.co.uk> (raw)
In-Reply-To: <CAGfcS_kqQKVQLZm+ZOVpkuiCm1=q3Hq6y6keRPk=+5v+-sdG0g@mail.gmail.com>
On 19/06/2014 12:56, Rich Freeman wrote:
> On Thu, Jun 19, 2014 at 7:44 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
>> On Thu, 19 Jun 2014 16:40:08 +0800, Amankwah wrote:
>>
>>> Maybe the only solution is that move the portage tree to HDD??
>>
>> Or tmpfs if you rarely reboot or have a fast enough connection to your
>> preferred portage mirror.
>
> There has been a proposal to move it to squashfs, which might
> potentially also help.
>
> The portage tree is 700M uncompressed, which seems like a bit much to
> just leave in RAM all the time.
The tree will not necessarily be left in RAM all of the time. Pages
allocated by tmpfs reside in pagecache. Given sufficient pressure, they
may be migrated to swap. Even then, zswap [1] could be used so as to
reduce write amplification. I like Neil's suggestion, assuming that the
need to reboot is infrequent.
--Kerin
[1] https://www.kernel.org/doc/Documentation/vm/zswap.txt
next prev parent reply other threads:[~2014-06-19 12:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 2:36 [gentoo-user] [Gentoo-User] emerge --sync likely to kill SSD? microcai
2014-06-19 8:40 ` Amankwah
2014-06-19 11:44 ` Neil Bothwick
2014-06-19 11:56 ` Rich Freeman
2014-06-19 12:16 ` Kerin Millar [this message]
2014-06-19 22:03 ` Full Analyst
2014-06-20 17:48 ` [gentoo-user] " Kai Krakow
2014-06-21 4:54 ` microcai
2014-06-21 14:27 ` Peter Humphrey
2014-06-21 14:54 ` Rich Freeman
2014-06-21 19:19 ` [gentoo-user] " Kai Krakow
2014-06-21 19:24 ` Kai Krakow
2014-06-22 1:40 ` Rich Freeman
2014-06-22 11:44 ` [gentoo-user] " Kai Krakow
2014-06-22 13:44 ` Rich Freeman
2014-06-24 18:34 ` [gentoo-user] " Kai Krakow
2014-06-24 20:01 ` Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53A2D4B5.3060805@fastmail.co.uk \
--to=kerframil@fastmail.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox