From: Judd Tracy <jtracy@ist.ucf.edu>
To: linux-lvm@redhat.com
Subject: [linux-lvm] High loads when writting to LVM
Date: Wed, 27 Oct 2004 11:14:05 -0400 [thread overview]
Message-ID: <417FBB3D.6060002@ist.ucf.edu> (raw)
I have a system that I am testing out lvm on to get a feeling about
stability and performance. Stability right now seems good, but I am a
little worried about the performance currently I am writing out a large
file ~1TB using dd if=/dev/zero of=test bs=1M and am noticing the load
seams extreamly high "5.21, 5.26, 5.17". Most of the work is being done
in dd but I also notice that kswapd0 is also working fairly heavily. Is
this to be expected with LVM or do i have things setup wrong. Write
performance seems to be around 100MB/s on an XFS filesystem.
System:
Opteron 242 1.4Ghz
2 GB RAM
Tyan S2882
3W-9000-12 in raid-5 with one hot spare
12 Seagate 250MB SATA drives
Fedora Core 2
Kernel 2.6.8-1.521
Judd Tracy
jtracy@ist.ucf.edu
next reply other threads:[~2004-10-27 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 15:14 Judd Tracy [this message]
2004-10-27 15:27 ` [linux-lvm] High loads when writting to LVM Paul Warren
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=417FBB3D.6060002@ist.ucf.edu \
--to=jtracy@ist.ucf.edu \
--cc=linux-lvm@redhat.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