From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Ed Sweetman <ed.sweetman@wmich.edu>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: Benchmarks for performance patches (-ck) for 2.4.19
Date: Mon, 2 Sep 2002 09:39:10 +0200 [thread overview]
Message-ID: <20020902093910.G781@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <3D72E267.6090502@wmich.edu>; from ed.sweetman@wmich.edu on Mon, Sep 02, 2002 at 12:00:39AM -0400
Hi Ed,
Hi Rik,
Hi lkml,
On Mon, Sep 02, 2002 at 12:00:39AM -0400, Ed Sweetman wrote:
> I dont experience audio cutouts with anything i do, even the really
> abusive things to the computer. I've only had it cut out when using
> bonnie or dbench and that's something you should expect. So what i see
> as responsiveness is switching windows on the same desktop and switching
> between virtual desktops. I see responsiveness as the time between i do
> something and the time it takes to redraw it. Using a G450, I expect a
> certain level of hardware performance and half a second or so to redraw
> a screen is not what i call responsive for a Tbird system. This is of
> course all X related because i dont see much or any problem with the
> console and with the kernel. At least nothing compared to X latencies.
This is not only X. The problem is the software layering bloat.
Thats a design mistake we copied from W*ndows in our Linux
applications.
Take your favorite - and I mean your favorite, not the easiest -
application, find the handler for the problem event, try to do a
really complete call graph trough all software layers involved
(say from read(inputdevice_fd) to get the event up to
write(outputdevice_fd) to write to the framebuffer) and count
cycles. Don't forget the cache misses due to following pointers,
which lead to random, non-local memory access patterns
(read: a VM and cache nightmare).
Once you really finish this boring task completely you know our
real performance problem.
Felix von Leitner did a nice presentation on our
Chemnitzer Linux Tag (but in German) and many experienced
programmers and software enginieers were really stunned.
So the problem is not really the kernel or the X layer. The
NUMBER of abstraction layers is the issue to attack.
People tend to import big bloated libraries or even completely
overkill operating systems just because it has ONE SIMPLE
property the actually need[1]. This must change.
Regards
Ingo Oeser
[1] Buying/Reselling Windows NT licenses + some Windows FTP
server license just because we need FTP. Buying WinCE
licenses, just because the embedded device must be able to be
accessible via TCP/IP. More examples available per private
mail. Stupidity has no limit here.
--
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth
next prev parent reply other threads:[~2002-09-02 11:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 1:10 Con Kolivas
2002-09-02 2:03 ` Ed Sweetman
2002-09-02 2:32 ` Rik van Riel
2002-09-02 4:00 ` Ed Sweetman
2002-09-02 7:39 ` Ingo Oeser [this message]
2002-09-02 13:20 ` Rik van Riel
2002-09-03 3:16 ` jw schultz
2002-09-02 5:22 ` Paul
2002-09-02 5:40 ` J Sloan
2002-09-02 5:57 ` Andrew Morton
2002-09-02 3:24 Dieter Nützel
2002-09-02 3:41 ` Rik van Riel
2002-09-02 3:42 ` Con Kolivas
2002-09-02 4:21 ` Randy.Dunlap
2002-09-02 9:12 Con Kolivas
2002-09-04 3:39 ` Paul
2002-09-02 12:50 Martin Knoblauch
2002-09-04 5:15 Wade
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=20020902093910.G781@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=ed.sweetman@wmich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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®