Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| wiki:system_configuration [2021/01/16 17:53] – autostatic | wiki:system_configuration [2021/02/18 10:24] – [Disabling resource-intensive daemons, services and processes] autostatic | ||
|---|---|---|---|
| Line 80: | Line 80: | ||
| Now reboot and you should have threaded IRQs. | Now reboot and you should have threaded IRQs. | ||
| + | |||
| + | === Disabling Spectre and Meltdown mitigations === | ||
| + | :!: Warning: disabling these mitigations will make your machine less secure! Use with caution! | ||
| + | |||
| + | To work around the Spectre and Meltdown vulnerabilities several mitigations were built into the kernel. These mitigations can have a negative impact on the performance of your machine. To disable those mitigations and get the most out of your CPU's again you can add the following kernel parameter to your Grub configuration: | ||
| + | |||
| + | mitigations=off | ||
| === Installing a real-time kernel === | === Installing a real-time kernel === | ||
| Line 229: | Line 236: | ||
| * Power management daemons like powersaved or kpowersave | * Power management daemons like powersaved or kpowersave | ||
| * CPU frequency scaling daemons that scale the frequency of the CPU depending on the CPU load could cause xruns in some cases. More recent versions of Jack1 (>= 0.118.0) are suffering less from xruns or run xrun free with a CPU frequency scaling daemon enabled that's set to a scaling governor like ondemand. A specialized CPU scaling daemon is in the works that depends on the DSP-load instead of the CPU load: [[http:// | * CPU frequency scaling daemons that scale the frequency of the CPU depending on the CPU load could cause xruns in some cases. More recent versions of Jack1 (>= 0.118.0) are suffering less from xruns or run xrun free with a CPU frequency scaling daemon enabled that's set to a scaling governor like ondemand. A specialized CPU scaling daemon is in the works that depends on the DSP-load instead of the CPU load: [[http:// | ||
| - | * Debian/ | ||
| * Desktop Environments (DE): especially on less powerful machines it is recommended to use a lighter DE than Gnome, KDE or Unity. Possible alternatives include LXDE, XFCE or IceWM. Another option is to only use a lightweight Window Manager (WM) like Openbox or Fluxbox. | * Desktop Environments (DE): especially on less powerful machines it is recommended to use a lighter DE than Gnome, KDE or Unity. Possible alternatives include LXDE, XFCE or IceWM. Another option is to only use a lightweight Window Manager (WM) like Openbox or Fluxbox. | ||
| * Compositing: | * Compositing: | ||
| * Gnome NetworkManager and WiFi: NetworkManager keeps scanning for new wireless networks in the background and this might cause xruns. The best option is to not use a wireless network manager in a low-latency real-time audio environment. If you really can't do without WiFi you probably won't have another option than to use wpa_supplicant. | * Gnome NetworkManager and WiFi: NetworkManager keeps scanning for new wireless networks in the background and this might cause xruns. The best option is to not use a wireless network manager in a low-latency real-time audio environment. If you really can't do without WiFi you probably won't have another option than to use wpa_supplicant. | ||
| - | * NTP: there are reports of NTP interfering with FFADO, so if you're using a FireWire audio device make sure you disable the ntpd service and any cronjob or ifup script that tries to sync your local clock with an NTP server. This issue is resolved in the 2.1.0 release of FFADO. | ||
| * D-Bus controlled services like '' | * D-Bus controlled services like '' | ||
| - | * Hardware support modules. | ||
| === CPU frequency scaling === | === CPU frequency scaling === | ||