From: Julian Calaby <julian.calaby@gmail.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
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: Mon, 7 Feb 2011 14:59:26 +1100 [thread overview]
Message-ID: <AANLkTim8Qt25C+L+R3e-R2qW0K6XxQBv-Fsy8K=aVA2H@mail.gmail.com> (raw)
In-Reply-To: <4D4F1A3D.2090107@hardwarefreak.com>
On Mon, Feb 7, 2011 at 09:01, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> Justin Piszcz put forth on 2/6/2011 4:16 AM:
>
>> Workflow process-
>>
>> Migrate data from old/legacy RAID sets to new ones, possibly also 2TB->3TB, so
>> the faster the transfer speed, the better.
>
> This type of data migration is probably going to include many many files of
> various sizes from small to large. You have optimized your system performance
> only for individual large file xfers. Thus, when you go to copy directories
> containing hundreds or thousands of files of various sizes, you will likely see
> much lower throughput using a single copy stream. Thus if you want to keep that
> 10 GbE pipe full, you'll likely need to run multiple copies in parallel, one per
> large parent directory. Or, run a single copy from say, 10 legacy systems to
> one new system simultaneously, etc.
>
> Given this situation, you may want to consider tar'ing up entire directories
> with gz or bz compression, if you have enough free space on the legacy machines,
> and copying the tarballs to the new system. This will maximize your throughput,
> although I don't know if it will decrease your total work flow completion time,
> which should really be your overall goal.
Another option might be to use tar and gzip to bundle the data up,
then pipe it through netcat or ssh. When I have to transfer large
chunks of data I find this is the fastest method. That said, if the
connection is interrupted, then you're on your own. rsync might also
be a good option.
Thanks,
--
Julian Calaby
Email: julian.calaby@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/
.Plan: http://sites.google.com/site/juliancalaby/
prev parent reply other threads:[~2011-02-07 3:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 19:35 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
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 [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='AANLkTim8Qt25C+L+R3e-R2qW0K6XxQBv-Fsy8K=aVA2H@mail.gmail.com' \
--to=julian.calaby@gmail.com \
--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 \
--cc=linux@treblig.org \
--cc=stan@hardwarefreak.com \
/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
all inboxes | Powered by JetHome®