public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Troeder <daniel@admin-box.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Normal disk speed?
Date: Wed, 06 Oct 2010 20:52:05 +0200	[thread overview]
Message-ID: <4CACC555.309@admin-box.com> (raw)
In-Reply-To: <AANLkTim_xL_pLTizGtJcpGqL_7ET7fdXiiXFw7npC5rK@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

On 10/06/2010 10:04 AM, Adam Carter wrote:
> FYI some braindead benchmarking, reiserfs vs ext4, kernel 2.6.35-gentoo-r8
> 
> Copy same DVD image from internal reiserfs drive to freshly formatted
> external drive;
> reiserfs    1m37.530s
> ext4        3m15.074s
> 
> Then image copy on that external drive;
> # time cp CentOS-5.3-x86_64-bin-DVD.iso CentOS-5.3-x86_64-bin-DVD.iso2
> # time cp CentOS-5.3-x86_64-bin-DVD.iso CentOS-5.3-x86_64-bin-DVD.iso3
> reiser        1m44.719s and 1m51.441s
> ext4        3m24.337s and 4m30.534s
> 
> Not that is matters, but create filesystem on 2TB drive;
> reiserfs    1m17.373s
> ext4        6m3.421s    
> 
> Didnt see that coming, I guess i'll stick with reiser3....
WOW! Those differences are crazy!

Please - I know benchmarking takes a lot of time - but could you check
something: the behavior those fs have at what time they flush data from
cache to disk is very different. Have you made sure that you measured
the time it really needs? I mean the difference between:

$ sync; time cp source dest
and
$ sync; time (cp source dest; sync)

Only the last measures somewhat correctly.

I'm irritated, because ext4 is extends based, and should behave much
better with big files than reiser3... not only less fragmentation, but
should also be faster...

Bye,
Daniel

-- 
PGP key @ http://pgpkeys.pca.dfn.de/pks/lookup?search=0xBB9D4887&op=get
# gpg --recv-keys --keyserver hkp://subkeys.pgp.net 0xBB9D4887


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2010-10-06 18:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 10:58 [gentoo-user] Normal disk speed? Adam Carter
2010-09-30 13:10 ` Florian Philipp
2010-09-30 16:00   ` Peter Humphrey
2010-09-30 16:12     ` [gentoo-user] " Nikos Chantziaras
2010-09-30 16:50     ` [gentoo-user] " Florian Philipp
2010-09-30 21:43       ` Peter Humphrey
2010-09-30 13:26 ` [gentoo-user] " James
2010-09-30 16:53 ` [gentoo-user] " Volker Armin Hemmann
2010-10-01  1:12   ` Adam Carter
2010-10-01  4:41     ` Volker Armin Hemmann
2010-10-01  8:42     ` Florian Philipp
2010-10-01 16:23       ` Volker Armin Hemmann
2010-10-02  2:11         ` Adam Carter
2010-10-02 11:54         ` Florian Philipp
2010-10-02 12:11           ` Volker Armin Hemmann
2010-10-02 12:44             ` Florian Philipp
2010-10-02 15:06               ` Florian Philipp
2010-10-01  9:05     ` Daniel Troeder
2010-10-01 14:40       ` [gentoo-user] " James
2010-10-02 17:29         ` Daniel Troeder
2010-10-03  0:13           ` James
2010-10-06  8:04             ` Adam Carter
2010-10-06 18:52               ` Daniel Troeder [this message]
2010-10-06 22:59                 ` Adam Carter
2010-10-07  9:33                   ` Daniel Troeder
2010-10-18 10:03                     ` Adam Carter

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=4CACC555.309@admin-box.com \
    --to=daniel@admin-box.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