From: Ismael Valladolid Torres <ismael@sambara.org>
To: "Michel Dänzer" <daenzer@debian.org>
Cc: linux-audio-dev@music.columbia.edu,
linux-audio-user@music.columbia.edu,
alsa-devel@lists.sourceforge.net,
alsa-user@lists.sourceforge.net, debian-powerpc@lists.debian.org
Subject: Re: Measuring latency on my Apple G3
Date: Mon, 21 Jul 2003 13:46:41 +0200 [thread overview]
Message-ID: <3F1BD2A1.7030404@sambara.org> (raw)
In-Reply-To: <1058785796.28382.139.camel@thor.holligenstrasse29.lan>
Michel Dänzer escribio el 21/07/03 13:09:
> First of all, you mentioned in another post that you use x11perf to
> create X11 stress. Are there also problems with real world apps?
"Real world" apps work properly (except for the Gnome theme manager
which displays garbage). I only find video performance using Linux a lot
lower than using any of the Mac OS's.
> Also keep in mind that neither the vanilla 2.4 kernel nor the X server
> were designed for low latency. Have you tried the low latency and/or
> O(1) scheduler kernel patches, and not running the X server with
> negative nice values if you are?
Both of those patches (A. Morton and R. Love's ones) were applied to my
kernel. I don't know about running the X server with different nice
values, which advantage would I get? (I am using gdm as my X session
manager).
> Last but possibly not least of all, the dmasound driver has been less
> prone to dropouts in my experience than the ALSA driver.
I should try with pure OSS. Let's not forget that the latency test suite
is using the OSS compatibility layer of ALSA.
Thanks a lot. Any feedback is still very useful.
Regards, Ismael
next prev parent reply other threads:[~2003-07-21 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 9:58 Measuring latency on my Apple G3 Ismael Valladolid Torres
2003-07-21 11:09 ` Michel Dänzer
2003-07-21 11:46 ` Ismael Valladolid Torres [this message]
2003-07-22 0:22 ` Michel Dänzer
2003-07-22 11:32 ` Ismael Valladolid Torres
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=3F1BD2A1.7030404@sambara.org \
--to=ismael@sambara.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=daenzer@debian.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linux-audio-dev@music.columbia.edu \
--cc=linux-audio-user@music.columbia.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.