From: Mike Galbraith <efault@gmx.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: gcoady@gmail.com, Jan Engelhardt <jengelh@linux01.gwdg.de>,
Willy Tarreau <willy@w.ods.org>,
Arjan van de Ven <arjan@infradead.org>,
j4K3xBl4sT3r <jakexblaster@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Which kernel is the best for a small linux system?
Date: Thu, 16 Mar 2006 10:20:44 +0100 [thread overview]
Message-ID: <1142500844.10098.26.camel@homer> (raw)
In-Reply-To: <1142499323.10098.14.camel@homer>
On Thu, 2006-03-16 at 09:55 +0100, Mike Galbraith wrote:
> On Thu, 2006-03-16 at 03:31 -0500, Lee Revell wrote:
> > On Thu, 2006-03-16 at 09:12 +0100, Mike Galbraith wrote:
> > > P.S. if you're talking about ssh console slowdown thingie, as I write
> > > this I'm ssh'd into my P3/500, and..
> > >
> > > [root]:# time w
> >
> > > real 0m0.033s
> > > user 0m0.013s
> > > sys 0m0.019s
> > > [root]:#
> >
> > I think you left out the result for 2.4.
>
> I don't have a 2.4 kernel. But no matter, I don't think it's going to
> get much better than .033s. Even if it did, .033s sure doesn't feel
> sluggish to me.
>
> Running ab from the other box is a bit slower since ssh is using the
> same net ab is blasting (only net I have)..
>
> [root]:# time netstat|grep :81|wc -l
> 1645
>
> real 0m0.259s
> user 0m0.133s
> sys 0m0.126s
>
> ...but still not what I'd call a slug.
Oops. Wrong kernel. That was one of my twiddled kernels. This is
2.6.15 doing the same ab across the net.
[root]:# time netstat|grep :81|wc -l
1592
real 3m7.502s
user 0m0.119s
sys 0m0.146s
Ouch!!
-Mike
next prev parent reply other threads:[~2006-03-16 9:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 0:40 Which kernel is the best for a small linux system? j4K3xBl4sT3r
2006-03-13 8:00 ` Lexington Luthor
2006-03-15 1:35 ` Grant Coady
2006-03-15 1:46 ` Randy.Dunlap
2006-03-13 8:17 ` Arjan van de Ven
2006-03-13 18:03 ` Grant Coady
2006-03-13 18:06 ` Arjan van de Ven
2006-03-14 6:21 ` Willy Tarreau
2006-03-14 7:29 ` Ingo Molnar
2006-03-14 8:18 ` Mike Galbraith
2006-03-14 9:05 ` Mike Galbraith
2006-03-14 15:54 ` Willy Tarreau
2006-03-16 15:24 ` Mike Galbraith
2006-03-14 10:03 ` Grant Coady
2006-03-14 22:21 ` Russell King
2006-03-15 0:46 ` Grant Coady
[not found] ` <20060315080313.GC3166@flint.arm.linux.org.uk>
2006-03-15 9:37 ` Grant Coady
2006-03-15 22:53 ` Jan Engelhardt
2006-03-15 23:32 ` Grant Coady
2006-03-16 4:19 ` Mike Galbraith
2006-03-16 8:12 ` Mike Galbraith
2006-03-16 8:31 ` Lee Revell
2006-03-16 8:55 ` Mike Galbraith
2006-03-16 9:20 ` Mike Galbraith [this message]
2006-03-16 2:55 ` Valdis.Kletnieks
2006-03-13 18:27 ` Sam Ravnborg
2006-03-13 18:41 ` Lee Revell
2006-03-13 19:01 ` Adrian Bunk
2006-03-14 0:18 ` j4K3xBl4sT3r
2006-03-13 19:08 ` Diego Calleja
2006-03-13 22:00 ` Pantelis Antoniou
2006-03-13 22:01 ` j4K3xBl4sT3r
2006-03-13 22:20 ` Pantelis Antoniou
2006-03-13 22:33 ` j4K3xBl4sT3r
2006-03-16 12:03 ` Pavel Machek
2006-03-13 22:25 ` Lee Revell
2006-03-14 3:53 ` Grant Coady
2006-03-15 22:57 ` Jan Engelhardt
2006-03-15 23:10 ` Adrian Bunk
2006-03-16 13:39 ` linux-os (Dick Johnson)
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=1142500844.10098.26.camel@homer \
--to=efault@gmx.de \
--cc=arjan@infradead.org \
--cc=gcoady@gmail.com \
--cc=jakexblaster@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=willy@w.ods.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