From: Chris Snook <csnook@redhat.com>
To: Andre Noll <maan@systemlinux.org>
Cc: "adam radford" <aradford@gmail.com>,
"Tony Battersby" <tonyb@cybernetics.com>,
"Johannes Wörner" <johannes.woerner@tuebingen.mpg.de>,
"James Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Performance problems with 3ware 9500S-4LP and 2.6.25-rc3
Date: Tue, 26 Feb 2008 13:33:36 -0500 [thread overview]
Message-ID: <47C45B80.6090907@redhat.com> (raw)
In-Reply-To: <20080226174314.GA30767@skl-net.de>
Andre Noll wrote:
> we are experiencing massive performance problems with two of our
> Linux servers that contain 3ware controllers on a Tyan mainboard and
> a couple of 1T disks.
>
> During the daily cron job that uses rsync to sync a 500G file system
> from another machine to the raid on the 3ware controller the load
> jumps up, and the machine becomes sluggish as hell. For example, an
> ssh login to that machine takes minutes to complete and ldap becomes
> unreliable while the rsync job is running. Even Nagios complains
> about the machine being down while rsync is running.
You're putting your box under astronomical load. This is generally
regarded as a bad idea, regardless of how well your storage controller
is performing. Can you measure the single-threaded throughput (say,
coping one huge file, and then syncing) to give us a baseline
performance figure? rsync will happily peg your box, your network, and
your cat if you let it.
-- Chris
next prev parent reply other threads:[~2008-02-26 18:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 17:43 Performance problems with 3ware 9500S-4LP and 2.6.25-rc3 Andre Noll
2008-02-26 17:54 ` Bernd Schubert
2008-02-27 10:10 ` Andre Noll
2008-02-26 18:33 ` Chris Snook [this message]
2008-02-27 10:11 ` Andre Noll
2008-02-27 19:55 ` Chris Snook
2008-02-28 9:46 ` Andre Noll
2008-02-26 23:07 ` Arnd Hannemann
2008-02-27 10:11 ` Andre Noll
2008-02-27 14:26 ` Tony Battersby
2008-02-27 17:05 ` Andre Noll
2008-02-27 20:06 ` adam radford
2008-02-28 9:46 ` Andre Noll
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=47C45B80.6090907@redhat.com \
--to=csnook@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aradford@gmail.com \
--cc=johannes.woerner@tuebingen.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maan@systemlinux.org \
--cc=tonyb@cybernetics.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 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.