public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andrew M. Theurer" <atheurer@austin.ibm.com>
To: lse-tech@lists.sourceforge.net,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	samba-technical <samba-technical@samba.org>
Subject: Linux 2.4 Scalability, Samba, and Netbench
Date: Wed, 09 May 2001 11:29:22 -0500	[thread overview]
Message-ID: <3AF97062.42465A53@austin.ibm.com> (raw)

Hello,

I am evaluating Linux 2.4 SMP scalability, using Netbench(r) as a
workload with Samba, and I wanted to get some feedback on results so
far.  I would appreciate comments and any suggestions for improving
scalability on this workload.

The environment consists of an Intel Profusion based SMP with 8 x 700
Mhz Xeon, 1 Mb L2, 14+ GB ram, ServeRAID, 8 Intel ethernet cards (IBM
Netfinity 8500R).  There are 16 500 Mhz PII, 128 MB clients running
Windows NT.  I tested for uniprocessor, 2-way, and 4-way SMP
configurations.  Future plans including testing 8-way performance when
more test clients are available.  Netbench(r) 7.01 was used with the
enterprise disk suite test.  The test was modified to use 2 engines per
client, and the range of test clients was changed from 1-60 to 8-16 
(for 2P & 4P) and 4-12 (for uniprocessor).

My initial results for linux 2.4.0, ext2 are as follows:

		[UP]	[2P]	[4P]
	08	149
	12	199
	16	227	236	260
# Eng	20	193	272	317	Mbps
	24	223	283	369
	28		285	396
	32		285	405

Same test, but with IRQ to processor affinity for 2P & 4P on the 8
ethernet cards:
		  	[2P]	[4P]
	16		231	259
# Eng	20		278	297
	24		293	320	Mbps
	28		297	365
	32		299	399*
	*Still investigating; we had some cpu idle time
	 on the 4P/32 engines, but not on test configuration
	 with out IRQ aff.

And for linux 2.4.3 with reiserfs:
		[UP]	[2P]	[4P]
	08	130
	12	190
	16	203	210	231
# Eng	20	190	235	279
	24	200	249	319	Mbps
	28		239	360
	32		251	335

Same, but with IRQ affinity for 2P & 4P on the 8 ethernet cards:
			[2P]	[4P]
	16		224	236
# Eng	20		220	308
	24		252	331	Mbps
	28		269	375
	32		267	382

 --All results in Mbps, using Netbench(r) 7.0.1 and Samba 2.0.7
 --Netbench(r) is available at http://www.netbench.com

I would like to help improve SMP scalability on this workload.  If you
have questions or comments about the above results, or if you are
conducting similar tests, please send email to
lse-tech@lists.sourceforge.net.  I have some ideas on my next steps,
but would like to discuss first.

Regards,

Andrew Theurer

             reply	other threads:[~2001-05-09 16:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-09 16:29 Andrew M. Theurer [this message]
2001-05-09 16:56 ` Linux 2.4 Scalability, Samba, and Netbench Mike Kravetz
2001-05-09 17:30   ` Andrew M. Theurer
2001-05-09 17:35     ` [Lse-tech] " Christoph Hellwig
2001-05-09 17:39     ` Alan Cox
2001-05-09 17:43       ` Andrew M. Theurer
2001-05-09 23:35       ` Chris Evans
2001-05-10  4:51     ` [Lse-tech] " Maneesh Soni
2001-05-10  8:40     ` Dipankar Sarma
2001-05-11 15:20       ` David Collier-Brown
2001-05-10  1:23 ` Kenichi Okuyama
  -- strict thread matches above, loose matches on Subject: below --
2001-05-09 23:34 Bruce Allan
2001-05-10 13:38 ` Andrew M. Theurer

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=3AF97062.42465A53@austin.ibm.com \
    --to=atheurer@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=samba-technical@samba.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