Scott Ecker wrote:
hollunder(a)gmx.at wrote:
> On Wed, 21 Oct 2009 23:25:36 -0700
> Scott <lau(a)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.
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.