| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| wiki:system_configuration [2017/05/29 16:56] – [Disabling resource-intensive daemons, services and processes] autostatic | wiki:system_configuration [2017/05/29 17:05] – [limits.conf/audio.conf] autostatic |
|---|
| === DBus-controlled services === | === DBus-controlled services === |
| |
| DBus is a solid standard used for a wide variety of services which need to be started automatically, but on demand only, in the background, not specifically at boot. One set of DBus services used extensively in Ubuntu is 'gvfs', the virtual filesystem for the Gnome desktop; if these are permitted to run, polling of hardware including the USB bus will occur, which is likely to interfere with USB MIDI interfaces, eat CPU power, and cause xruns in general. To disable gvfs, go as root to ''/usr/share/dbus-1/services'', rename ''gvfs-daemon.service'' to ''gvfs-daemon.service.disabled'', and rename ''gvfs-metadata.service'' to ''gvfs-metadata.service.disabled''. | DBus is a solid standard used for a wide variety of services which need to be started automatically, but on demand only, in the background, not specifically at boot. One set of DBus services used extensively in Ubuntu is 'gvfs', the virtual filesystem for the Gnome desktop; if these are permitted to run, polling of hardware including the USB bus will occur, which is likely to interfere with USB MIDI interfaces, eat CPU power, and cause xruns in general. To disable gvfs, become root and run the follwing two commands: |
| | mv /usr/share/dbus-1/servicesgvfs-daemon.service /usr/share/dbus-1/servicesgvfs-daemon.service.disabled |
| | mv /usr/share/dbus-1/services/gvfs-metadata.service /usr/share/dbus-1/servicesgvfs-metadata.service.disabled |
| |
| === Hardware support modules === | === Hardware support modules === |
| recovery.//"((http://elinux.org/images/b/b6/EMMC-SSD_File_System_Tuning_Methodology_v1.0.pdf)) | recovery.//"((http://elinux.org/images/b/b6/EMMC-SSD_File_System_Tuning_Methodology_v1.0.pdf)) |
| |
| You can't use this parameter in ''/etc/fstab'' for the root partition, you will have to set it as a kernel parameter. So when using Grub you can add the following parameter to the ''GRUB_CMDLINE_LINUX_DEFAULT'' line in ''/etc/default/grub'': | You can't use this parameter in ''/etc/fstab'' for the root partition, you will have to set it as a kernel parameter. So when using Grub you can add the following parameter to the ''GRUB_CMDLINE_LINUX'' line in ''/etc/default/grub'': |
| rootflags=data=writeback | rootflags=data=writeback |
| | |
| @audio - memlock unlimited # maximum locked-in-memory address space (KB) | @audio - memlock unlimited # maximum locked-in-memory address space (KB) |
| |
| Setting ''memlock'' to ''unlimited'' shouldn't be strictly necessary since most apps would work fine with lower values (such as ''500000'').\\ | Setting ''memlock'' to ''unlimited'' shouldn't be strictly necessary since most apps would work fine with lower values (such as ''500000''). However, certain applications have been reported to complain or even to crash with lower values than ''unlimited''. On the other hand, giving unlimited capability of locking memory can cause buggy applications to temporarily freeze the whole system. See http://www.linuxmusicians.com/viewtopic.php?f=10&t=2193 for more details. |
| However, certain applications have been reported to complain or even to crash with lower values than ''unlimited''.\\ | |
| On the other hand, giving unlimited capability of locking memory can cause buggy applications to temporarily freeze the whole system.\\ | |
| See http://www.linuxmusicians.com/viewtopic.php?f=10&t=2193 for more details. | |
| |
| You could also allow the audio group to renice processes with the help of the ''limits.conf'' file, but since nice uses SCHED_OTHER it basically does nothing to increase the performance of a low-latency real-time audio environment that relies on SCHED_FIFO/SCHED_RR. Consult the //sched_setscheduler// manpage for more info on this subject. | You could also allow the audio group to renice processes with the help of the ''limits.conf'' file, but since nice uses SCHED_OTHER it basically does nothing to increase the performance of a low-latency real-time audio environment that relies on SCHED_FIFO/SCHED_RR. Consult the //sched_setscheduler// manpage for more info on this subject. |
