public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [Gentoo-User] emerge --sync likely to kill SSD?
Date: Sat, 21 Jun 2014 15:27:48 +0100	[thread overview]
Message-ID: <2770815.rPAQsmKHEU@wstn> (raw)
In-Reply-To: <un8e7b-pne.ln1@hurikhan77.spdns.de>

On Friday 20 June 2014 19:48:14 Kai Krakow wrote:
> microcai <microcai@fedoraproject.org> schrieb:
> > 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.
> 
> Use a file system that turns random writes into sequential writes, like the
> pretty newcomer f2fs. You could try using it for your rootfs but currently I
> suggest just creating a separate partition for it and either mount it as
> /usr/portage or symlink that dir into this directory (that way you could
> use it for other purposes, too, that generate random short writes, like log
> files).

Well, there's a surprise! Thanks for mentioning f2fs. I've just converted my 
Atom box's seven partitions to it, recompiled the kernel to include it, 
changed the fstab entries and rebooted. It just worked.

--->8

> I'd also suggest not to use the discard mount options and instead create a
> cronjob that runs fstrim on the SSD devices. But YMMV.

I found that fstrim can't work on f2fs file systems. I don't know whether 
discard works yet.

Thanks again.

-- 
Regards
Peter



  parent reply	other threads:[~2014-06-21 14:27 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
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 [this message]
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=2770815.rPAQsmKHEU@wstn \
    --to=peter@prh.myzen.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