All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] unusual writing speeds when benchmark speeds are high enough
Date: Mon, 18 Mar 2013 11:43:59 +0100	[thread overview]
Message-ID: <20130318104359.GA8350@citd.de> (raw)
In-Reply-To: <20130318100148.GA1399@fancy-poultry.org>

On 18.03.2013 11:01, Heinz Diehl wrote:
> On 18.03.2013, Matthias Schniedermeyer wrote: 
> 
> > The SSD i have can reach (with encryption) about 400MB/s, but that is 
> > best-case performance when all moons are aligned. I haven't really 
> > benchmarked the real-world performance, the dd-example (with conv=fsync) 
> > only got 88MB/s.
> 
> On all my SSD disks, cryptsetup performance is not even near that. I
> have about 450 MB/s without encryption, and max. 120 MB/s with. 

SSD performance has more 'it depends' than anything else.
It isn't funny. ;-)

But as i don't need my SSDs for write-heavy linear performance (much), 
the much better random-write rate than HDDs still make them worthwile. 
And the much better (random) read performance is the icing.


Overwriting appers to have better performance, but that is nothing i 
would do regularly.
dd if=/dev/zero of=zero bs=1M count=10k oflag=direct
10737418240 bytes (11 GB) copied, 116.629 s, 92.1 MB/s

dd if=/dev/zero of=zero bs=1M count=10k oflag=direct conv=notrunc
10737418240 bytes (11 GB) copied, 50.3905 s, 213 MB/s

dd if=/dev/zero of=zero bs=1M count=10k oflag=direct conv=notrunc
10737418240 bytes (11 GB) copied, 51.0608 s, 210 MB/s


My previous SSD with a Sandforce controller had much worse "worst case" 
performance as the Sandforce controller really doesn't like 
incompressible data and encrypted data looks like (or at least should 
look like) incompressible random-data.



-- 

Matthias

  parent reply	other threads:[~2013-03-18 10:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-17 21:36 [dm-crypt] unusual writing speeds when benchmark speeds are high enough .. ink ..
2013-03-17 22:55 ` Matthias Schniedermeyer
2013-03-18  6:42   ` .. ink ..
2013-03-18  8:37     ` Matthias Schniedermeyer
2013-03-18 10:01       ` Heinz Diehl
2013-03-18 10:20         ` Arno Wagner
2013-03-18 10:43         ` Matthias Schniedermeyer [this message]
2013-03-17 23:07 ` Arno Wagner
2013-03-17 23:19   ` .. ink ..
2013-03-18  6:22     ` Milan Broz
2013-03-18  7:58       ` .. ink ..
2013-03-18 18:16   ` .. ink ..
2013-03-18  7:06 ` Heinz Diehl

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=20130318104359.GA8350@citd.de \
    --to=ms@citd.de \
    --cc=dm-crypt@saout.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.