From: "JaniD++" <djani22@dynamicweb.hu>
To: Lajber Zoltan <lajbi@lajli.gau.hu>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID0 performance question
Date: Sat, 26 Nov 2005 18:34:20 +0100 [thread overview]
Message-ID: <01f901c5f2af$a4312550$0400a8c0@dcccs> (raw)
In-Reply-To: Pine.LNX.4.58.0511261810350.1482@lajli.gau.hu
Hello, Zoltán!
----- Original Message -----
From: "Lajber Zoltan" <lajbi@lajli.gau.hu>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-raid@vger.kernel.org>
Sent: Saturday, November 26, 2005 6:11 PM
Subject: Re: RAID0 performance question
> On Sat, 26 Nov 2005, JaniD++ wrote:
>
> > Hello, Raz,
> >
> > Think this is not cpu usage problem. :-)
> > The system is divided to 4 cpuset, and each cpuset uses only one
disknode.
> > (CPU0->nb0, CPU1->nb1, ...)
>
> Seams to be CPU problem. Which kind of NIC do you have?
Intel xeon motherboard, intel e1000 x2. (64bit)
But i already write that, if i cut out the raid, and starts the 4 cat at one
time the traffic is rise to 780-800 Mbit! :-)
This is not hardware related problem.
Only tune, or missconfiguration problem. - I think...
>
> > CPU2 states: 2.0% user 74.0% system 0.0% nice 3.0% iowait 18.0%
> > idle
> > CPU3 states: 10.0% user 57.0% system 0.0% nice 5.0% iowait 26.0%
>
> Do you have 4 cpu, or 2 HT cpu?
2x HT :-)
But in the previous top, it was an used system!
Thanks,
Janos
>
> Bye,
> -=Lajbi=----------------------------------------------------------------
> LAJBER Zoltan Szent Istvan Egyetem, Informatika Hivatal
> Most of the time, if you think you are in trouble, crank that throttle!
> -
> 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
-
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
next prev parent reply other threads:[~2005-11-26 17:34 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++ [this message]
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++
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='01f901c5f2af$a4312550$0400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=lajbi@lajli.gau.hu \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).