Re: [LAU] Test if Linux is ready for audio (realtimeconfigquickscan.pl script)

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Scott <lau@...>
To: linux-audio-user <linux-audio-user@...>
Date: Thursday, October 22, 2009 - 9:32 pm

This is a multi-part message in MIME format.
--------------060409090204030701010400
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

rosea grammostola wrote:

>From the horse's mouth:

> It has to do with Python's lack of support for signals in threads.

-Scott

--------------060409090204030701010400
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

rosea grammostola wrote:

Scott Ecker wrote:

hollunder@gmx.at wrote:

On Wed, 21 Oct 2009 23:25:36 -0700
Scott <lau@troutpocket.org> wrote:

Ken Restivo wrote:

But it also caught this other weird thing I'd never heard of:
fs.inotify.max_user_watches = 524288

Which was easy enough to fix.

What sort of problem were you having that changing that setting fixed?

-Scott

I'm also very curious about this one as I've never heard of it before
and haven't seen any help that explains what it does.

+1 , I think it was found in the Rosegarden wiki maybe?

It wrongly assumes a tmpfs has to be on /tmp and nice doesn't help with
rt stuff afaik.

I think its in the FAQ of jackaudio.org

I'm also not quite sure about the filesystem related stuff it checks
for, like the use of atime or whatever.

I'd say the script is a nice start but nothing to rely on or use as
definitiv guideline.

It would be nice if could improve the script by more feedback of people
here on LAU

Since we're on the subject of improving performance I should share one
little thing I learned recently. I use Fedora+CCRMA. The Fedora update
manager is python based. After disabling the automatic update service I
eradicated virtually all xruns. I asked a more knowledgeable friend why
this may be and he told me that Python is/can be greedy with resources.
YMMV.

Thanks, good tip.

>From the horse's mouth:

It has to do with Python's lack of support for
signals in threads.

https://bugzilla.gnome.org/show_bug.cgi?id=481569

http://dev.laptop.org/ticket/4680

The Red Hat people have put a lot of work into fixing this, along with
Sugar.

Python apps which initialize threads will end up waking every 1/10th of
a second, rather than idling properly.

-Scott

--------------060409090204030701010400--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] Test if Linux is ready for audio, Jonathan E. Brickman, (Tue Oct 20, 12:42 am)
Re: [LAU] Test if Linux is ready for audio, Ken Restivo, (Thu Oct 22, 6:18 am)
Re: [LAU] Test if Linux is ready for audio, Scott, (Thu Oct 22, 6:25 am)
Re: [LAU] Test if Linux is ready for audio, Scott Ecker, (Thu Oct 22, 4:19 pm)
Re: [LAU] Test if Linux is ready for audio (realtimeconfigqu..., rosea grammostola, (Thu Oct 22, 4:27 pm)
Re: [LAU] Test if Linux is ready for audio (realtimeconfigqu..., Scott, (Thu Oct 22, 9:32 pm)
Re: [LAU] Test if Linux is ready for audio (realtimeconfigqu..., Jonathan E. Brickman, (Thu Oct 22, 10:39 pm)
Re: [LAU] Test if Linux is ready for audio, Ray Rashif, (Tue Oct 20, 1:40 am)
Re: [LAU] Test if Linux is ready for audio, James Cameron, (Tue Oct 20, 7:47 am)
Re: [LAU] Test if Linux is ready for audio, Ray Rashif, (Tue Oct 20, 7:45 am)