public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Cc: Alex Schuster <wonko@wonkology.org>
Subject: Re: [gentoo-user] SSD performance tweaking
Date: Sun, 26 Aug 2012 13:53:49 +0200	[thread overview]
Message-ID: <1726832.5OjJhh9kq3@energy> (raw)
In-Reply-To: <503A0B55.3030206@wonkology.org>

Am Sonntag, 26. August 2012, 13:41:09 schrieb Alex Schuster:
> Frank Steinmetzger writes:
>  > On Thu, Aug 23, 2012 at 12:15:20PM +0200, Alex Schuster wrote:
> >> The size of an erasable block of SSDs is even larger, usually 512K, it
> >> would be best to align to that, too. A partition offset of 512K or 1M
> >> would avoid this.
> > 
> > Unless the filesystem knows this and starts bigger files at those 512 k
> > boundaries (so really only one erase cycle is needed for files <=512 k),
> > isn't this fairly superfluous?
> 
> Yes, I think it is. When you search for SSD alignment, you read about
> this alignment all the time, even on the German Wikipedia, and many
> resources say that this can have a big impact on performance. But I
> could not find a real explanation at all.
> 
> Besides that, it's not so easy to do the alignment, at least when using
> LVM. I read that LVM adds 192K header information, so even if you align
> the partition start to an erasable block size of 512K, the actual
> content is not aligned. See [*] for information how to overcome this.
> That is, if you believe the alignment to erasable blocks is important,
> personally I do not know what to think now. It wouldn't hurt, so why not
> apply it, but it seems like snake oil to me now.
> 
> 	Wonko
> 
> http://tytso.livejournal.com/2009/02/20/

because erasing is slow. You can not overwrite data on a ssd. you have to 
erase first, then reprogramm. Also, erasing shortens lifetime. 

-- 
#163933


  reply	other threads:[~2012-08-26 11:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 21:46 [gentoo-user] SSD performance tweaking Mark Knecht
2012-08-22 22:58 ` Paul Hartman
2012-08-22 23:24   ` Dale
2012-08-23  4:05     ` Mark Knecht
2012-08-23 12:55       ` J. Roeleveld
2012-08-23 15:55   ` Mark Knecht
2012-08-23 18:57     ` Mark Knecht
2012-08-23 19:22       ` Neil Bothwick
2012-08-23 19:30         ` Michael Mol
2012-08-23 20:38           ` Mark Knecht
2012-08-23 20:50             ` Michael Mol
2012-08-23 19:34         ` Mark Knecht
2012-08-23 19:43           ` Michael Mol
2012-08-23 21:37             ` Neil Bothwick
2012-08-23  8:14 ` Volker Armin Hemmann
2012-08-23 10:15 ` Alex Schuster
2012-08-24  9:25   ` Frank Steinmetzger
2012-08-25 22:22     ` Volker Armin Hemmann
2012-08-26  2:04       ` Frank Steinmetzger
2012-08-26 12:54         ` Allan Gottlieb
2012-08-26 11:41     ` Alex Schuster
2012-08-26 11:53       ` Volker Armin Hemmann [this message]
2012-08-26 12:49         ` Alex Schuster
2012-08-26 14:21           ` Volker Armin Hemmann
2012-08-26 16:14             ` Alex Schuster
2012-08-26 16:35               ` Volker Armin Hemmann
2012-08-27 15:58               ` Paul Hartman
2012-08-26 20:49       ` Neil Bothwick

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=1726832.5OjJhh9kq3@energy \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=wonko@wonkology.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