Page 1 of 4
Wiki update
Posted: Tue Oct 23, 2018 5:46 pm
by khz
<EDIT>
Welcome! If you inform yourself about GNU/Linux, e.g. in the wiki, and find outdated, further, new entries you can report it immediately, you are invited to contribute.
>> Register and log in to the wiki (https://wiki.linuxaudio.org/wiki/start?do=login§ok= || https://wiki.linuxaudio.org/wiki/editor_notes) to edit posts or create new ones. Thank you, we are LM! ! <<</EDIT>
Since I often read that the information from
https://wiki.linuxaudio.org is (partly) outdated, my suggestion is:
Collect the obsolete entries here with the current correct correction worked out in community.
We can then add them to the wiki, i.e. bring the wiki up to date.
In my opinion this would help everyone.
https://linuxmusicians.com ==
https://wiki.linuxaudio.org IMHO
Re: Wiki update
Posted: Tue Dec 18, 2018 6:53 pm
by khz
@
https://wiki.linuxaudio.org/wiki/system ... #quickscan Please correct the entry
to
Code: Select all
perl -I ./ ./realTimeConfigQuickScan.pl
, THX.
<EDIT>
done</EDIT>
Re: Wiki update
Posted: Tue Dec 18, 2018 8:29 pm
by raboof
Actually "perl ./realTimeConfigQuickScan.pl" is correct since
https://github.com/raboof/realtimeconfi ... an/pull/23
Re: Wiki update
Posted: Tue Dec 18, 2018 8:41 pm
by lilith
JackWinter mentioned several times in various threads that the reatimeconfig script is outdated and many points are not necessary. Mabye it needs a major rehaul?
Re: Wiki update
Posted: Tue Dec 18, 2018 8:50 pm
by raboof
lilith wrote:JackWinter mentioned several times in various threads that the reatimeconfig script is outdated and many points are not necessary. Mabye it needs a major rehaul?
Contributions are very welcome!
Re: Wiki update
Posted: Tue Dec 18, 2018 9:31 pm
by khz
Oh, just new "git clone" and tested, now it works. Great, I had not noticed that.
Thank you!
lilith wrote:JackWinter mentioned several times in various threads that the reatimeconfig script is outdated and many points are not necessary. Mabye it needs a major rehaul?
That's why I opened this thread, among other things.
Instead of just saying what is wrong or outdated it would be more constructive to list it here. Ideally with a correct or current correction suggestion.
Re: Wiki update
Posted: Tue Dec 18, 2018 10:15 pm
by khz
@realTimeConfigQuickScan
==>
max_user_watches
The "increase max_user_watches by adding 'fs.inotify.max_user_watches = 524288'" I find confusing. For a newcomer, perhaps even more confusing.
There are references on the net on adjusting the fs.inotify.max_user_watches value also for enhanced performance. But it remains very unclear where these references come from and if adjusting this value actually does anything at all. The max_user_watches parameter sets the maximum number of files your system can monitor with inotify (which is part of the kernel) for changes. Setting this parameter too low results in inotify failing. Setting it too high can make inotify needlessly consume memory. Best is to not touch the default settings as setting this parameter is unrelated to performance in an audio context.
http://wiki.linuxaudio.org/wiki/system_ ... sysctlconf
==>
tmpfs
The
Code: Select all
** Warning: no tmpfs partition mounted on /tmp
should be changed.
It should search for "shm". See here for details:
viewtopic.php?p=93108#p93108
Re: Wiki update
Posted: Tue Dec 18, 2018 10:31 pm
by raboof
khz wrote:@realTimeConfigQuickScan
==>
max_user_watches
The "increase max_user_watches by adding 'fs.inotify.max_user_watches = 524288'" I find confusing. For a newcomer, perhaps even more confusing.
There are references on the net on adjusting the fs.inotify.max_user_watches value also for enhanced performance. But it remains very unclear where these references come from and if adjusting this value actually does anything at all. The max_user_watches parameter sets the maximum number of files your system can monitor with inotify (which is part of the kernel) for changes. Setting this parameter too low results in inotify failing. Setting it too high can make inotify needlessly consume memory. Best is to not touch the default settings as setting this parameter is unrelated to performance in an audio context.
http://wiki.linuxaudio.org/wiki/system_ ... sysctlconf
Couldn't there be applications like DAWs or samplers that have a lot of files open?
Perhaps we should split the advice in 'basic' and 'advanced' tuning, and move this to the 'advanced' at least?
That check has been removed since
https://github.com/raboof/realtimeconfi ... an/pull/19
Re: Wiki update
Posted: Wed Dec 19, 2018 1:24 pm
by khz
raboof wrote:Couldn't there be applications like DAWs or samplers that have a lot of files open?
I don't have any idea. Possible.
raboof wrote:Perhaps we should split the advice in 'basic' and 'advanced' tuning, and move this to the 'advanced' at least?
Agree.
Ah, okay, I missed that too. Whereby I find the basic idea of at that time "tmpfs" later then "shm" in the RAM great to move out since the audio in the RAM is worked off faster and the hard disk spares. I would take that into the realTimeConfigQuickScan.
Re: Wiki update
Posted: Wed Dec 19, 2018 2:28 pm
by raboof
khz wrote:Whereby I find the basic idea of at that time "tmpfs" later then "shm" in the RAM great to move out since the audio in the RAM is worked off faster and the hard disk spares. I would take that into the realTimeConfigQuickScan.
I'm not sure I understand what you mean, but all means PR a proposal
Re: Wiki update
Posted: Wed Dec 19, 2018 2:40 pm
by khz
"Shm" - back then "tmps" - outsources the jack audio processes to RAM.
The RAM is faster than writing to the hard disk and the hard disk is spared.
Re: Wiki update
Posted: Wed Dec 19, 2018 2:46 pm
by raboof
khz wrote:"Shm" - back then "tmps" - outsources the jack audio processes to RAM.
The RAM is faster than writing to the hard disk and the hard disk is spared.
Yes, it would be great to check that there is indeed a tmpfs mounted on /dev/shm, which JACK would use. PR welcome!
Re: Wiki update
Posted: Mon Dec 31, 2018 12:38 am
by lilith
Is it safe to delete the reatimeconfig directory (wonder why it's root root) to get the new version from git. Was there any important change?
Code: Select all
marco@fox:~/realtimeconfigquickscan$ ll
insgesamt 108
-rw-r--r-- 1 root root 1350 Apr 20 2018 AudioGroupCheck.pm
-rw-r--r-- 1 root root 1606 Apr 20 2018 BackgroundCheck.pm
-rw-r--r-- 1 root root 1275 Apr 20 2018 Check.pm
-rw-r--r-- 1 root root 18008 Apr 20 2018 COPYING
-rw-r--r-- 1 root root 1734 Apr 20 2018 GovernorCheck.pm
-rw-r--r-- 1 root root 1737 Apr 20 2018 HighResTimersCheck.pm
-rw-r--r-- 1 root root 1654 Apr 20 2018 HpetCheck.pm
-rw-r--r-- 1 root root 1863 Apr 20 2018 Hz1000Check.pm
-rw-r--r-- 1 root root 1500 Apr 20 2018 KernelConfigCheck.pm
-rw-r--r-- 1 root root 1543 Apr 20 2018 MultiAudioCheck.pm
-rw-r--r-- 1 root root 1886 Apr 20 2018 NoAtimeCheck.pm
-rw-r--r-- 1 root root 1744 Apr 20 2018 NoHzCheck.pm
-rw-r--r-- 1 root root 1567 Apr 20 2018 PreemptRtCheck.pm
-rw-r--r-- 1 root root 2220 Apr 20 2018 QuickScanEngine.pm
-rwxr-xr-x 1 root root 2078 Apr 20 2018 QuickScan.pl
-rw-r--r-- 1 root root 820 Apr 20 2018 README.md
-rwxr-xr-x 1 root root 4061 Apr 20 2018 realTimeConfigQuickScan.pl
-rw-r--r-- 1 root root 1364 Apr 20 2018 RootCheck.pm
-rw-r--r-- 1 root root 1681 Apr 20 2018 RtcCheck.pm
-rw-r--r-- 1 root root 1509 Apr 20 2018 RtprioCheck.pm
-rw-r--r-- 1 root root 1790 Apr 20 2018 SwappinessCheck.pm
-rw-r--r-- 1 root root 1606 Apr 20 2018 SysCtlCheck.pm
-rw-r--r-- 1 root root 1534 Apr 20 2018 WatchesCheck.pm
Re: Wiki update
Posted: Mon Dec 31, 2018 10:18 am
by noedig
On another note: on the
http://linuxaudio.org/ page, when you click on Resources, this link:
Code: Select all
lowlatency.linuxaudio.org Linux Audio Low-Latency Performance How-To
points to a very outdated wiki page. Can this be removed? I think a single link to the wiki (already present) is sufficient IMHO.
Also, the quicktools link points to an odd, outdated site. Is this link necessary?
Re: Wiki update
Posted: Mon Dec 31, 2018 1:10 pm
by raboof
lilith wrote:Is it safe to delete the reatimeconfig directory
Yes, that should be safe
lilith wrote:wonder why it's root root
You probably (accidentally) were root when you first got it.
lilith wrote:Was there any important change?
There were a couple of neat improvements, but nothing very big. See
https://github.com/raboof/realtimeconfi ... its/master