Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| wiki:system_configuration [2021/03/01 21:29] – [sysctl.conf] autostatic | wiki:system_configuration [2021/03/01 21:30] – [sysctl.conf] autostatic |
|---|
| This setting changes the so-called swappiness of your system, or in other words, the moment when your system starts to use its swap partition. You can check the current value with ''cat /proc/sys/vm/swappiness'', in most cases it is set to 60. This is too high, it will make your system start using swap too fast which might influence the overall performance. | This setting changes the so-called swappiness of your system, or in other words, the moment when your system starts to use its swap partition. You can check the current value with ''cat /proc/sys/vm/swappiness'', in most cases it is set to 60. This is too high, it will make your system start using swap too fast which might influence the overall performance. |
| |
| There are references on the net on adjusting the ''fs.inotify.max_user_watches'' value also for enhanced performance. 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. The advise of increasing this value might originate from for example DAW's or samplers that watch a lot of files and if the system runs out of watchers these DAW's or samplers fall back to polling the file system which increases disk IO which could in turn cause jitter. And since modern systems have mostly enough memory these days increasing this value should cause no issues. | There are references on the net on adjusting the ''fs.inotify.max_user_watches'' value also for enhanced performance. 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. The advise of increasing this value might originate from for example DAW's or samplers that watch a lot of files and if the system runs out of watchers these DAW's or samplers fall back to polling the file system which increases disk IO which could in turn cause jitter((https://linuxmusicians.com/viewtopic.php?p=129194#p129194)). And since modern systems have mostly enough memory these days increasing this value should cause no issues. |
| |
| ==== audio group ==== | ==== audio group ==== |
