public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: gcoady@gmail.com
Cc: 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 09:12:28 +0100	[thread overview]
Message-ID: <1142496748.10098.5.camel@homer> (raw)
In-Reply-To: <1142482749.8369.12.camel@homer>

On Thu, 2006-03-16 at 05:19 +0100, Mike Galbraith wrote:
> On Thu, 2006-03-16 at 10:32 +1100, Grant Coady wrote:
> > 
> > Certainly provides little motivation for testers to provide any 
> > feedback does it not?  I've had two threads on sluggish terminal 
> > here performance without resolution.  2.6 feels sluggish, the test 
> > is simple and repeatable, your ridicule does not change that at all.
> 
> Hmm.  You have a testcase that's both simple _and_ repeatable?  Cool.
> What is it?

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
 09:07:02 up  2:44,  6 users,  load average: 3.74, 4.09, 3.34
USER     TTY        LOGIN@   IDLE   JCPU   PCPU  WHAT
root     tty1      06:23   10:11   0.17s  0.15s  -bash
root     tty2      08:43   23:34  41.09s 41.05s  top d1
root     tty3      08:49   22.00s  0.12s  0.10s  -bash
root     tty4      08:51    3:50   4.05s  3.95s  ab -c 50 -n 10000
http://localhost 81
root     tty5      09:04    1:12   0.06s  0.05s  -bash
root     pts/0     08:38    0.00s  0.18s  0.02s  w

real    0m0.033s
user    0m0.013s
sys     0m0.019s
[root]:#        


  reply	other threads:[~2006-03-16  8:11 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 [this message]
2006-03-16  8:31                     ` Lee Revell
2006-03-16  8:55                       ` Mike Galbraith
2006-03-16  9:20                         ` Mike Galbraith
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=1142496748.10098.5.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=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