public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "" <jamagallon@ono.com>
Cc: Emmanuel Florac <eflorac@intellique.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RAID-1 performance under 2.4 and 2.6
Date: Thu, 27 Mar 2008 17:49:05 -0400	[thread overview]
Message-ID: <47EC1651.7090300@tmr.com> (raw)
In-Reply-To: <8CAC9F9E-60FE-40A5-A720-27BA63BEEADC@ono.com>

J.A. Magallón wrote:

> But you shouldn't have to tweak anything.
> Let's forget for a moment calling dd a 'benchmark'. The fact is that a
> certain program (in its default behaviour, dd if=xxx of=yyy) is waaay
> slower in 2.6 than in 2.4. So something has gone nuts.

Ah, agreement from another direction. Yes, portable solutions often use 
tools like awk, grep, and sed, which do just the very thing which make 
2.6 unhappy. And to claim that this is a vm problem (hopefully not) and 
that Linux is no longer good at complex tasks like copying a large file 
a line at a time, at leat unless you have GBs of memory so it can 
"scale," I really hope that's very wrong.

> The typical question is 'who cares dd ?'. And the answer: all normal
> applications that just read and write, that do not use any *advise()
> because they tried to be portable, that are not rewritten and fancy
> optimized to take advantage of latest kernel knobs, in short, any normal
> app that just fopen()s and fread()s...

Major company seen in the news which has custom QA hardware which writes 
one very long line of ASCII every 100ms for 17hrs, and now they have to 
read it with awk or perl and write info to multiple data files.

> Seriously, are people telling that I have to tweak my app to get the
> same performance that in 2.4 ? The basic performance should be the same,
> and all those knobs should let you get _better_ throughput, not just the
> same. To say anything else is to hide the head on the floor...
> 
I just copied an 8GB DVD image from one drive to another. I checked, it 
doesn't go through a dial-up modem, it's just painfully *slow*.

I think the problem is that many developers *do* use big machines, with 
fast disk, lots of memory, and don't spend much time using (or making 
useful) more typical desktop configurations. And yes, these are "real" 
applications, and they run better on 2.4.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


  reply	other threads:[~2008-03-27 21:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 18:43 RAID-1 performance under 2.4 and 2.6 Emmanuel Florac
2008-03-25 22:00 ` Chris Snook
2008-03-25 22:09   ` Emmanuel Florac
2008-03-25 22:47   ` Bill Davidsen
2008-03-25 23:13     ` Chris Snook
2008-03-25 23:42       ` Bill Davidsen
2008-03-26  8:05         ` Emmanuel Florac
2008-03-26  8:25           ` "J.A. Magallón"
2008-03-27 21:49             ` Bill Davidsen [this message]
2008-03-26 16:51           ` Chris Snook
2008-03-26 16:39         ` Chris Snook
2008-07-16 14:52       ` Pádraig Brady
2008-07-16 18:18         ` Chris Snook
2008-03-26  7:15   ` Bart Van Assche
2008-03-26  7:56     ` Emmanuel Florac
2008-03-27 21:53     ` Bill Davidsen
2008-03-28  7:44       ` Bart Van Assche
2008-03-28 12:04         ` Bill Davidsen
2008-03-25 22:37 ` Bill Davidsen
2008-03-26  8:42 ` Bart Van Assche
2008-03-26 11:07   ` Emmanuel Florac
2008-03-26 11:15     ` Bart Van Assche
2008-03-26 12:36       ` Emmanuel Florac
2008-03-26 13:22         ` Bart Van Assche
2008-03-27 22:03         ` Bill Davidsen

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=47EC1651.7090300@tmr.com \
    --to=davidsen@tmr.com \
    --cc=eflorac@intellique.com \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.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