From: TJ <systemloc@earthlink.net>
To: linux-raid@vger.kernel.org
Cc: Guy <bugzilla@watkins-home.com>
Subject: Re: Looking for the cause of poor I/O performance
Date: Fri, 3 Dec 2004 01:33:07 -0500 [thread overview]
Message-ID: <200412030133.07743.systemloc@earthlink.net> (raw)
In-Reply-To: <200412030354.iB33sD913132@www.watkins-home.com>
> My linux system is a P3-500 with 2 CPUs and 512 Meg RAM. My system is much
> faster than my network. I don't know how your K6-500 compares to my
> P3-500. But RAM may be your issue. That amount of ram seems very low. Are
> you swapping? What is your CPU load during the tests? If you are at 100%,
> then you are CPU bound.
You've got a dual CPU setup, mine is only single. I'll bet you have a server
chipset too. Still, I have serious doubts that the CPU is at fault. My guess
would be that this could be a VIA chipset problem. The load averages while
running these tests are allways well below 1.
I mistyped the amount of memory. I have approx 409 MB. I am not swapping.
> Your disk performance is faster than a 100BaseT network. So, your
> performance may not be an issue.
The network is gigabit, with a crossover to the client machine. I used ttcp to
verify that the link is capable of over 146 MB/sec.
TJ
next prev parent reply other threads:[~2004-12-03 6:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 16:38 Looking for the cause of poor I/O performance TJ
2004-12-03 0:49 ` Mark Hahn
2004-12-03 3:54 ` Guy
2004-12-03 6:33 ` TJ [this message]
2004-12-03 7:38 ` Guy
2004-12-04 15:23 ` TJ
2004-12-04 17:59 ` Guy
2004-12-04 23:51 ` Mark Hahn
2004-12-05 1:00 ` Steven Ihde
2004-12-06 17:48 ` Steven Ihde
2004-12-06 19:29 ` Guy
2004-12-06 21:10 ` David Greaves
2004-12-06 23:02 ` Guy
2004-12-08 9:24 ` David Greaves
2004-12-08 18:31 ` Guy
2004-12-08 22:00 ` Steven Ihde
2004-12-08 22:25 ` Guy
2004-12-08 22:41 ` Guy
2004-12-09 1:40 ` Steven Ihde
2004-12-12 8:56 ` Looking for the cause of poor I/O performance - a test script David Greaves
2004-12-28 0:13 ` Steven Ihde
2004-12-06 21:16 ` Looking for the cause of poor I/O performance Steven Ihde
2004-12-06 21:42 ` documentation of /sys/vm/max-readahead Morten Sylvest Olsen
2004-12-05 2:16 ` Looking for the cause of poor I/O performance Guy
2004-12-05 15:14 ` TJ
2004-12-06 21:39 ` Mark Hahn
2004-12-05 15:17 ` TJ
2004-12-06 21:34 ` Mark Hahn
2004-12-06 23:06 ` Guy
2004-12-03 6:51 ` TJ
2004-12-03 20:03 ` TJ
2004-12-04 22:59 ` Mark Hahn
2004-12-03 7:12 ` TJ
-- strict thread matches above, loose matches on Subject: below --
2004-12-03 11:30 TJ
2004-12-03 11:46 ` Erik Mouw
2004-12-03 15:09 ` TJ
2004-12-03 16:25 ` Erik Mouw
2004-12-03 16:32 ` David Greaves
2004-12-03 16:50 ` Guy
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=200412030133.07743.systemloc@earthlink.net \
--to=systemloc@earthlink.net \
--cc=bugzilla@watkins-home.com \
--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).