From: Nivedita Singhvi <nivedita@sequent.com>
To: linux-kernel@vger.kernel.org
Subject: netperf stream scaling; patches that help?
Date: Wed, 2 May 2001 12:18:56 -0700 (PDT) [thread overview]
Message-ID: <200105021918.MAA10107@eng4.sequent.com> (raw)
I'm trying to run a simple test on a pair of Linux 2.4.2
PC's that starts up simultaneous netperf tcp stream tests,
and find that I cant invoke more that 800 without running
into memory allocation failures. This wouldnt be strange
except that I find on the same systems, FreeBSD seems to
do twice as well (1600). I complete 500 concurrent netperf
tcp stream tests sending 64 byte packets successfully, but
again, FreeBSD completes a 1000 successfully. Also, Linux
appears to hog around 300MB on the server side, whereas
FreeBSD only appears to be using 3MB. Those are the bare
numbers, details available, of course, but what I'd like
to do is repeat the Linux test with 2.4.4 and include some
VM patches that might possibly alleviate any memory
management issues I may be running into.
This is between a 500MHz PIII Katmai and 333MHz PII
Deschutes both with 512MB memory, over a 100Mb (3C905C)
private nw.
I'd appreciate any pointers to patches that might help,
or suggestions in general to improve the Linux numbers.
Especially any insight into whether this is a case of
apples/oranges or whether I'm missing some trivial element
here...
I know of Ed Tomlinson's patch posted on this list on
4/12, are there any others? I know Jonathan Morton posted
some OOM patches, are those included in 2.4.4?
thanks,
Nivedita
---
Nivedita Singhvi (503) 578-4580
Linux Technology Center nivedita@us.ibm.com
IBM Beaverton, OR nivedita@sequent.com
reply other threads:[~2001-05-02 19:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200105021918.MAA10107@eng4.sequent.com \
--to=nivedita@sequent.com \
--cc=linux-kernel@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