linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Troy Wilson <tcw@tempest.prismnet.com>
To: akpm@digeo.com
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	lse-tech@lists.sourceforge.net
Subject: SPECWeb99 Data -- tcp-wakeups
Date: Wed, 25 Sep 2002 10:47:53 -0500 (CDT)	[thread overview]
Message-ID: <200209251547.g8PFlsrR013807@tempest.prismnet.com> (raw)

   ********************************************************************
   *  SPEC(tm) and the benchmark name SPECweb(tm) are registered      *
   *  trademarks of the Standard Performance Evaluation Corporation.  *
   *  This benchmarking was performed for research purposes only,     *
   *  and is non-compliant, with the following deviations from the    *
   *  rules -                                                         *
   *                                                                  *
   *    1 - It was run on hardware that does not meed the SPEC        *
   *        availability-to-the-public criteria.  The machine is      *
   *        an engineering sample.                                    *
   *                                                                  *
   *    2 - access_log wasn't kept for full accounting.  It was       *
   *        being written, but deleted every 200 seconds.             *
   ********************************************************************

  I've done some testing with SPECWeb99 on 2.5.35 mm1 with and without 
the tcp-wakeups patch backed out.  The addition of tcp-wakeups makes a 2%
improvement in performance.

                           mm1              mm1 without tcp-wakeup
                         -----------------------------------------
Simultaneous connections   3049             2982


  The system is an 8-way, 900MHz, Profusion-based P3 box with 32GB memory.
It's connected to 16 SPECWeb client machines via 4 e1000 gigabit adapters.
I'm using Apache 2.0.36 as the webserver.

- Troy




                 reply	other threads:[~2002-09-25 15:42 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=200209251547.g8PFlsrR013807@tempest.prismnet.com \
    --to=tcw@tempest.prismnet.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=netdev@oss.sgi.com \
    /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).