From: Eric Whiting <ewhiting@amis.com>
To: "Heflin, Roger A." <Roger.A.Heflin@conoco.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: huge number of intr/s on large nfs server
Date: Tue, 15 Oct 2002 17:05:03 -0600 [thread overview]
Message-ID: <3DAC9F1F.4B254A4D@amis.com> (raw)
In-Reply-To: 5CA6F03EF05E0046AC5594562398B9160C773F@poexmb3.conoco.net
"Heflin, Roger A." wrote:
>
> After doing some reading I figured out my mistake.
>
> Others had told me that it ran 4 pairs at 125Mhz each, and that it
> worked just like 100BT (1 bit per clock cycle), apparently they are
> sending 2bit per cycle so 2 bits x 125Mhz * 4 channels is
> 1Gbps, if they were only using 1 bit per cycle it would be
> only 50MB/second.
>
> What is your underlying setup to get the 93MB/second,
> ie disks/controllers/cpus?
Going OT here...
That 93MB/s is with an odd mix of systems:
1. AMD MP 2000+ dual
Tyan Motherboard
3G RAM
Netgear GA620
2. Intel Xeon 2.2G dual
? Motherboard
4G RAM
Motherboard Intel gigE
gigE nics are tied together with a crossover cable.
boxes were not idle, disks are slow, but ftp of a 1G file shows 93MB/s.
I'm sure others could do better -- I think I could do better. Actually
given my disks on those boxes I have to put to /dev/null to see the
93MB/s... Linux ide-raid list shows people with disks running 100+MB/s
-- my disks are not that fast...
eric
-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-10-15 23:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 21:40 huge number of intr/s on large nfs server Heflin, Roger A.
2002-10-15 23:05 ` Eric Whiting [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-15 19:27 Heflin, Roger A.
2002-10-15 20:51 ` Eric Whiting
2002-10-16 2:58 ` Eff Norwood
2002-10-16 2:54 ` Eff Norwood
2002-10-15 14:02 Heflin, Roger A.
2002-10-16 2:41 ` Eff Norwood
2002-10-14 20:21 Eff Norwood
2002-10-15 8:13 ` Bogdan Costescu
2002-10-15 16:50 ` Eff Norwood
2002-10-15 17:02 ` Bogdan Costescu
2002-10-15 21:22 ` Andrew Theurer
2002-10-16 20:06 ` Eff Norwood
2002-10-16 22:51 ` Donavan Pantke
2002-10-16 23:18 ` Eff Norwood
2002-10-16 23:28 ` Donavan Pantke
2002-10-17 2:28 ` Benjamin LaHaise
2002-10-17 2:49 ` Eff Norwood
2002-10-17 11:15 ` Alex Thiel
2002-10-17 16:42 ` Eff Norwood
2002-10-17 13:33 ` Andrew Theurer
2002-10-17 16:59 ` Eff Norwood
2002-10-18 2:05 ` Benjamin LaHaise
2002-10-18 2:19 ` Eff Norwood
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=3DAC9F1F.4B254A4D@amis.com \
--to=ewhiting@amis.com \
--cc=Roger.A.Heflin@conoco.com \
--cc=nfs@lists.sourceforge.net \
/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.