public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Amankwah <amankwah7@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [Gentoo-User] emerge --sync likely to kill SSD?
Date: Thu, 19 Jun 2014 16:40:08 +0800	[thread overview]
Message-ID: <20140619084008.GA97639@NAS> (raw)
In-Reply-To: <CAMgqO2x7B6qKhFs6a=s=5saaY4KLtMJEh-3Q=TBoePRMQWRhzQ@mail.gmail.com>

On Thu, Jun 19, 2014 at 10:36:59AM +0800, microcai wrote:
> rsync is doing bunch of  4k ramdon IO when updateing portage tree,
> that will kill SSDs with much higher Write Amplification Factror.
> 
> 
> I have a 2year old SSDs that have reported Write Amplification Factor
> of 26. I think the only reason is that I put portage tree on this SSD
> to speed it up.
> 
> what is the suggest way  to reduce Write Amplification  of a portage sync ?
> 

Maybe the only solution is that move the portage tree to HDD??


  reply	other threads:[~2014-06-19  8:40 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 [this message]
2014-06-19 11:44   ` Neil Bothwick
2014-06-19 11:56     ` Rich Freeman
2014-06-19 12:16       ` Kerin Millar
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=20140619084008.GA97639@NAS \
    --to=amankwah7@gmail.com \
    --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