linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Apurva Mehta <apurva@gmx.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] O11int for interactivity
Date: Wed, 30 Jul 2003 21:03:12 +0530	[thread overview]
Message-ID: <20030730153312.GB1341@home.woodlands> (raw)
In-Reply-To: <200307301038.49869.kernel@kolivas.org>

* Con Kolivas <kernel@kolivas.org> [30-07-2003 13:36]:
> Update to the interactivity patches. Not a massive improvement but
> more smoothing of the corners.
>
> [snip]
>
> _All_ testing and comments are desired and appreciated.

Well, I just put my system under severe natural load using
2.6.0-test2-mm1 and I must say that my system remained as responsive
as one could expect. I have a PentiumIII 500Mhz with 192 Mb RAM. 

Here's what load was like:
1) Compiling 2.6.0-test2-mm1-O11.1int :)
2) updating spamassassin bayesian filters (This mainly causes heavy
   disk i/o, the CPU usage is not so high)
3) procmail filtering ~40 emails simultaneously. 
4) playing ogg's in xmms 
5) switching between viewing pdf's and web-browsing

Window switching remained pretty snappy and there was one skip in
the music . The pdf's scrolled at a decent speed too.

All in all I would say that I really cannot expect anything more in
terms of responsiveness from my hardware. IMO, there is a limit to the
magic a good scheduler can do on limited hardware resources. 

The scheduler has certainly come a long way since 2.6.0-test1
( plus all subsequent patches and versions). Great work.

	   - Apurva

  parent reply	other threads:[~2003-07-30 15:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30  0:38 [PATCH] O11int for interactivity Con Kolivas
2003-07-30  0:55 ` Con Kolivas
2003-07-30  1:08   ` Con Kolivas
2003-07-31 13:55     ` Szonyi Calin
2003-07-31 13:56       ` Con Kolivas
2003-07-31 15:21       ` Måns Rullgård
2003-07-31 21:38       ` William Lee Irwin III
2003-07-31 22:01         ` Robert Love
2003-07-30  8:29 ` Felipe Alfaro Solana
2003-07-30  8:43   ` Marc-Christian Petersen
2003-07-30  9:38     ` Con Kolivas
2003-07-30  9:45       ` Marc-Christian Petersen
2003-07-30 12:56       ` Felipe Alfaro Solana
2003-07-30 13:14         ` Wade
2003-07-31 21:43     ` William Lee Irwin III
2003-07-31 21:55       ` William Lee Irwin III
2003-08-01 10:44       ` Marc-Christian Petersen
2003-08-02 21:27         ` Marc-Christian Petersen
2003-08-02 22:55           ` William Lee Irwin III
2003-08-02 23:19             ` Marc-Christian Petersen
2003-08-04 19:06               ` Marc-Christian Petersen
2003-08-04 19:53                 ` William Lee Irwin III
2003-08-05  0:56                   ` Nick Piggin
2003-08-05  2:41                     ` William Lee Irwin III
2003-08-05  3:07                       ` Nick Piggin
2003-08-05  3:13                         ` William Lee Irwin III
2003-08-05  3:23                           ` Nick Piggin
2003-08-05  3:31                             ` William Lee Irwin III
2003-08-05  3:38                               ` Nick Piggin
2003-08-05  4:54                                 ` Valdis.Kletnieks
2003-08-05  5:02                                   ` William Lee Irwin III
2003-08-05  5:55                                   ` Andrew Morton
2003-08-05  7:11                                     ` Nick Piggin
2003-08-05 17:00                                     ` Martin Josefsson
2003-07-30  8:41 ` Felipe Alfaro Solana
2003-07-30  9:35   ` Con Kolivas
2003-07-30 15:33 ` Apurva Mehta [this message]
2003-07-31 16:58 ` Moritz Muehlenhoff
2003-07-30 10:31 Voluspa
2003-07-30 10:51 ` Con Kolivas
2003-07-30 11:20   ` Eugene Teo

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=20030730153312.GB1341@home.woodlands \
    --to=apurva@gmx.net \
    --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;
as well as URLs for NNTP newsgroup(s).