From: Con Kolivas <kernel@kolivas.org>
To: Voluspa <lista1@telia.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] O16.2int
Date: Sun, 17 Aug 2003 00:09:06 +1000 [thread overview]
Message-ID: <200308170009.06461.kernel@kolivas.org> (raw)
In-Reply-To: <20030816130735.3ec67ac9.lista1@telia.com>
On Sat, 16 Aug 2003 21:07, Voluspa wrote:
> On 2003-08-16 8:59:48 Con Kolivas wrote:
> > Much simpler
>
> For a coder, perhaps. This user however is facing what feels like a
> fundamental flaw. The doubling of boot time was fixed, but game-test is
> pretty much as it was in pure O16 (impossible) and Blender is equally
> bad - now even the mouse pointer vanishes, becomes invisible, during the
> 10+ second pauses. And it is with Blender as only app running. Didn't
> dare to start xmms...
Nice.
Funny you should mention xmms in the same sentence since that's an app that
works fine. I was under no illusion that O16s were going to make these apps
perform well. Now you have to clarify what you mean by game test as being
impossible. I assume you mean wine based games? The only game I own is
neverwinternights and that performs beautifully. You have to tell me about
this blender app? I'm unable to fully reproduce these problems here as the
only thing exhibiting starvation is a mozilla plugin that is busy on wait
using the libgdk(something) library, and it is usable without starvation
albeit at sucky performance. If you can profile blender sucking it would be
helpful.
> I'll keep running the 2.6.0-test3 ---> O16.2int though. Might pick up
> other cases of regression in lighter usage.
It's not a matter of light versus heavy, it's only select applications. Try
running your machine at absurd loads (without hitting swap) with apps that
don't exhibit it.
Since these are the last thing in my gunsights for the interactivity
development I'd appreciate as much info as anybody has on what happens when
they suck, and if profiling can find a common link. Since I own none of the
apps that do this I can only try to fix them with your help. If someone is
available for frequent small patch testing that would also be helpful as that
helped the other interactivity development, so please email me directly.
Con
next prev parent reply other threads:[~2003-08-16 14:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 11:07 [PATCH] O16.2int Voluspa
2003-08-16 14:09 ` Con Kolivas [this message]
2003-08-16 14:41 ` Nick Piggin
2003-08-16 15:00 ` Con Kolivas
2003-08-16 14:44 ` Voluspa
-- strict thread matches above, loose matches on Subject: below --
2003-08-17 20:37 Benjamin Weber
2003-08-17 21:47 ` Tom Sightler
2003-08-18 1:21 ` Con Kolivas
2003-08-18 16:51 ` Antonio Vargas
2003-08-18 23:47 ` Con Kolivas
2003-08-16 9:02 Con Kolivas
2003-08-16 13:29 ` Wiktor Wodecki
2003-08-17 7:40 ` Andrew Morton
2003-08-17 9:30 ` Con Kolivas
2003-08-17 14:59 ` Con Kolivas
2003-08-17 21:06 ` Andrew Morton
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=200308170009.06461.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@telia.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