From: Matthias Schniedermeyer <ms@citd.de>
To: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] unusual writing speeds when benchmark speeds are high enough
Date: Mon, 18 Mar 2013 09:37:00 +0100 [thread overview]
Message-ID: <20130318083700.GA28049@citd.de> (raw)
In-Reply-To: <CAFnMBaQFkb3iKbL9vX0ofx1nMsF_c0e8YmtMibx8KbTAQ-wgfg@mail.gmail.com>
On 18.03.2013 02:42, .. ink .. wrote:
> I would say, there are quite a few details missing.
> > Hardware, Software?
> > 28.4 MB/s also isn't what i would call fast, what is that?
> >
> > The person responded and this is his computer spec:
>
> intel core 2 duo e8500
> 2 gb ram
> 2x 80 GB HDD western digital 7,200 RPM
> Kernel 3.2.18-pclos3.bfq
>
> 32bit os
>
> No LVM volume or RAID stuff,the test was done from the user home directory.
>
> What speed do you get from "dd" command?. People usually say the speeds i
> post are not high enough but i do not remember anybody saying what speeds
> are normal,expected.
My newest acquisition (got it friday), a 7200RPM HDD, does between
190MB/s (outer rim) and 90MB/s (inner rim).
The performance i got out of it yesterday, when i tried the dd command,
was 137MB/s (and 3.1 GB/s for the version without conv=fsync).
The HDD before that, a "green" model with around 5400 RPM, does between
130MB/s and 60MB/s.
The best performance i usually see in reality is about 110MB/s, but it
depends on where the files are written to and also where the source-file
was placed on the source-HDD, so in the worst-case is about 60MB/s.
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.
--
Matthias
next prev parent reply other threads:[~2013-03-18 8:37 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 [this message]
2013-03-18 10:01 ` Heinz Diehl
2013-03-18 10:20 ` Arno Wagner
2013-03-18 10:43 ` Matthias Schniedermeyer
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=20130318083700.GA28049@citd.de \
--to=ms@citd.de \
--cc=dm-crypt@saout.de \
--cc=mhogomchungu@gmail.com \
/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.