From: Apurva Mehta <apurva@gmx.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] O16int for interactivity
Date: Mon, 18 Aug 2003 15:38:53 +0530 [thread overview]
Message-ID: <20030818100853.GA1326@home.woodlands> (raw)
In-Reply-To: <200308160149.29834.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
* Con Kolivas <kernel@kolivas.org> [15-08-2003 22:21]:
[snip]
> Those who experienced starvation could you please test this patch.
O16.1int on top of 2.6.0-test3-mm1 is an improvement over O15int but
it still has some issues. Sound skips and general unresponsiveness
occur under relatively light load. For example, scrolling a PDF in
acrobat sometimes results in 2-3 second skips in sound. Also, the PDF
continues to scroll long after I have left the scroll button. While
scrolling, if I try to switch to Firebird or some other relatively
heavy app, there is a noticeable delay before it comes up. Sometimes
even an xterm running mutt takes a second to show while a PDF is
scrolling.
I was doing a `make htmldocs` while scrolling the pdf. That is all. In
O15int, the same behaviour would occur even if there was _nothing_
else running (except the browser window and xmms ofcourse). That is
the only improvement I have noticed.
I am attaching some numbers that were requested (vmstat, top and
readprofile outputs). These are generated from a script that was
posted here a few days ago. I am attaching the script so it is clear
what was done.
While this script was running, I was basically scrolling a PDF and one
long skip in sound was heard while doing so. I also kept switching
between application windows.
Hope this helps.
Regards,
- Apurva
--
Engineers motto: cheap, good, fast: choose any two
[-- Attachment #2: numbers.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 16379 bytes --]
next prev parent reply other threads:[~2003-08-18 10:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 15:49 Con Kolivas
2003-08-15 18:26 ` Timothy Miller
2003-08-15 18:45 ` Richard B. Johnson
2003-08-16 2:31 ` Con Kolivas
2003-08-18 15:46 ` Timothy Miller
2003-08-18 15:43 ` Nick Piggin
2003-08-18 19:48 ` Timothy Miller
2003-08-18 22:46 ` Nick Piggin
2003-08-15 19:00 ` Felipe Alfaro Solana
2003-08-16 2:14 ` [PATCH]O16.1int was " Con Kolivas
2003-08-15 21:01 ` Mike Fedyk
2003-08-15 23:03 ` Scheduler activations (IIRC) question Jamie Lokier
2003-08-15 23:54 ` Mike Fedyk
2003-08-16 0:54 ` Jamie Lokier
2003-08-16 6:14 ` Mike Galbraith
2003-08-16 14:18 ` Jamie Lokier
2003-08-17 5:51 ` Mike Galbraith
2003-08-17 6:55 ` Jamie Lokier
2003-08-17 7:05 ` Nick Piggin
2003-08-17 8:34 ` Mike Galbraith
2003-08-17 17:12 ` Jamie Lokier
2003-08-17 17:15 ` Arjan van de Ven
2003-08-17 18:26 ` Jamie Lokier
2003-08-17 18:27 ` Mike Galbraith
2003-08-17 18:29 ` Jamie Lokier
2003-08-17 18:46 ` Jamie Lokier
2003-08-16 20:54 ` Ingo Oeser
2003-08-16 21:39 ` Jamie Lokier
[not found] ` <20030817144203.J670@nightmaster.csn.tu-chemnitz.de>
2003-08-17 20:02 ` Jamie Lokier
2003-08-18 0:23 ` William Lee Irwin III
2003-08-18 10:38 ` Ingo Oeser
2003-08-18 13:09 ` Jamie Lokier
2003-08-16 7:01 ` [PATCH] O16int for interactivity Con Kolivas
2003-08-18 10:08 ` Apurva Mehta [this message]
2003-08-18 10:30 ` Con Kolivas
2003-08-18 12:13 ` Apurva Mehta
2003-08-15 20:50 Voluspa
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=20030818100853.GA1326@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
all inboxes | Powered by JetHome®