From: "Allen Curtis" <acurtis@onz.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: Debugging Network Performance
Date: Mon, 3 Jun 2002 20:27:33 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFMEBCDIAA.acurtis@onz.com> (raw)
I was wondering if anyone could provide some pointers on monitoring and
debugging network communications. The performance of Ethernet communications
seems to vary with kernel revisions. I would like to analyze this problem
but I need a little guidance on the issue.
TIA!
=========== Previous 8260 Ethernet email ==================
2. Some relative performance measurements (HHL 2.4.2 vs. 2.4.19pre9)
10T Hub | 100BT switch
-------------------------------------|
2.4.2 | 410KBps | 750KBps |
-------------------------------------|
2.4.19 | 440KBps | 190KBps |
--------------------------------------
RedHat 2.4.18-3 (x86) 3900KBps
3. TOP shows as much as 48% system utilization during a single FTP transfer.
With the fix mentioned in #1, there are 0 errors reported by ifconfig.
I may be missing something but I believe that these numbers are going the
wrong way. There is still the question of performance decrease when using a
100BT switch. Signal intregety can not be the only suspect considering the
performance did increase using an older version of the kernel. (although
nothing like the Workstation performance)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-06-04 3:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 3:27 Allen Curtis [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 4:34 Debugging Network Performance Allen Curtis
2002-06-04 9:50 ` Kenneth Johansson
2002-06-04 11:12 Mark Wisner
2002-06-04 13:30 ` Allen Curtis
2002-06-04 14:35 Mark Wisner
2002-06-04 14:46 ` Allen Curtis
2002-06-04 15:05 ` Michael Fischer
2002-06-05 5:18 Bill Fink
2002-06-05 13:16 ` Allen Curtis
2002-06-05 13:56 ` Bill Fink
2002-06-05 12:18 Jean-Denis Boyer
2002-06-05 13:35 ` Allen Curtis
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=NCBBIINEHIPFGJPLBEIFMEBCDIAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=linuxppc-dev@lists.linuxppc.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).