All of lore.kernel.org
 help / color / mirror / Atom feed
From: "JaniD++" <djani22@dynamicweb.hu>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID0 performance question
Date: Wed, 23 Nov 2005 10:44:36 +0100	[thread overview]
Message-ID: <007b01c5f012$89bdebd0$a700a8c0@dcccs> (raw)
In-Reply-To: 17322.12373.766596.426816@cse.unsw.edu.au


----- Original Message ----- 
From: "Neil Brown" <neilb@suse.de>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-raid@vger.kernel.org>
Sent: Thursday, December 22, 2005 5:49 AM
Subject: Re: RAID0 performance question


> On Tuesday November 22, djani22@dynamicweb.hu wrote:
> > I have already try the all available options, including readahead in all
> > layer (result in earlyer mails), and chunksize.
> > But with this settings, i cannot workaround this.
> > And the result is incomprehensible for me!
> > The raid0 performance is not equal with one component , with sum of all
> > component , and not equal with the slowest component!
>
> This is quite perplexing.
>
> My next step would probably be to watch the network traffic with
> tcpdump or ethereal.  I would look for any differences between when it
> is going quickly (without raid0) and when slowly (with raid0).
>
> Rather than tcpdump, it might be easier to instrument the nbd server
> to print out requests and timestamps.

Yes, it is good idea!
I will try it, thanks!

>
> Sorry I cannot be more helpful, and do have a Merry Christmas anyway
> :-)

The same to you, and everybody on this list! :-)

Cheers,
Janos

>
> NeilBrown
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2005-11-23  9:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 19:34 mdadm 2.1: command line option parsing bug? Andreas Haumer
2005-11-21 23:21 ` Neil Brown
2005-11-22 11:21   ` Michael Tokarev
2005-11-24  5:15     ` Neil Brown
2005-11-22 15:41   ` Molle Bestefich
2005-11-24  5:25     ` Neil Brown
2005-11-24  7:31       ` Ross Vandegrift
2005-12-15  1:53       ` Molle Bestefich
2005-12-15  4:19         ` Neil Brown
2005-12-15 10:37           ` Molle Bestefich
2005-11-22 22:05   ` Andre Noll
2005-11-26 14:04     ` RAID0 performance question JaniD++
2005-11-26 15:56       ` Raz Ben-Jehuda(caro)
2005-11-26 16:08         ` JaniD++
2005-11-26 17:11           ` Lajber Zoltan
2005-11-26 17:34             ` JaniD++
2005-11-26 19:47               ` Lajber Zoltan
2005-11-26 23:27       ` Neil Brown
2005-11-26 23:37         ` JaniD++
2005-11-27 15:39         ` Al Boldi
2005-11-27 16:21           ` JaniD++
2005-11-27 17:40             ` Al Boldi
2005-11-27 19:02               ` JaniD++
2005-11-30 23:13               ` JaniD++
2005-12-02 19:53                 ` Al Boldi
2005-12-18  0:13                   ` JaniD++
2005-12-19 11:16                     ` Al Boldi
2005-11-22  1:14                       ` JaniD++
2005-11-23 10:48                       ` JaniD++
2005-12-21  1:40                     ` Neil Brown
2005-11-22  1:56                       ` JaniD++
2005-12-22  4:49                         ` Neil Brown
2005-11-23  9:44                           ` JaniD++ [this message]

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='007b01c5f012$89bdebd0$a700a8c0@dcccs' \
    --to=djani22@dynamicweb.hu \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.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.