public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Emmanuel Florac <eflorac@intellique.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-net@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: Re: Supermicro X8DTH-6: Only ~250MiB/s from RAID<->RAID over 10GbE?
Date: Sat, 5 Feb 2011 22:06:21 +0000	[thread overview]
Message-ID: <20110205220621.GB17347@gallifrey> (raw)
In-Reply-To: <alpine.DEB.2.00.1102051553591.8518@p34.internal.lan>

* Justin Piszcz (jpiszcz@lucidpixels.com) wrote:
>
>
> On Sat, 5 Feb 2011, Emmanuel Florac wrote:
>
>> Le Sat, 5 Feb 2011 14:35:52 -0500 (EST) vous écriviez:
>>
>
> To respond to everyone:
>
>> Did you try launching 4 simultaneous cp operations over nfs to get to  
>> 1.2 GB/s?
>>  I've witnessed single stream copy performance with Samba being less than
>> maximum due to Samba limitations.  Running multiple copy ops in parallel then
>> usually saturates the pipe.
>
>
> I tried 4 simultaenous cp's and there was little change, 250-320MiB/s.

So I think you've said network benchmarks are OK, disc benchmarks are OK, but 
a copy over the network is slow.

What happens if you run a disc benchmark at the same time as a network benchmark;
even though the two aren't related? Can you keep the disc busy writing even when
the network is being pushed?

Dave
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\ gro.gilbert @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" 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:[~2011-02-05 22:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05 19:35 Supermicro X8DTH-6: Only ~250MiB/s from RAID<->RAID over 10GbE? Justin Piszcz
2011-02-05 19:42 ` Jean Gobin
2011-02-05 19:54   ` Justin Piszcz
2011-02-05 20:18   ` Justin Piszcz
2011-02-05 20:39     ` Stan Hoeppner
2011-02-05 20:45 ` Emmanuel Florac
2011-02-05 21:05   ` Justin Piszcz
2011-02-05 22:06     ` Dr. David Alan Gilbert [this message]
2011-02-05 22:30       ` Justin Piszcz
2011-02-05 22:56         ` Justin Piszcz
2011-02-05 23:54           ` Stan Hoeppner
2011-02-06  1:08             ` Justin Piszcz
2011-02-06  3:16               ` Stan Hoeppner
2011-02-06 10:16                 ` Justin Piszcz
2011-02-06 13:46                   ` Justin Piszcz
2011-02-06 16:44                     ` Emmanuel Florac
2011-02-06 16:55                     ` Zdenek Kaspar
2011-02-06 17:52                       ` Justin Piszcz
2011-02-06 22:01                   ` Stan Hoeppner
2011-02-07  3:59                     ` Julian Calaby

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=20110205220621.GB17347@gallifrey \
    --to=linux@treblig.org \
    --cc=ap@solarrain.com \
    --cc=eflorac@intellique.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=linux-scsi@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