Careful configuration of this, and the apps feeding into it, can significantly reduce the load- I played with this quite extensively but need to tinker again to nail down a configuration. The biggest chunk of CPU is usually due to the re-sampler, which takes whatever audio it’s given and re-samples it to be compatible with the output device it’s using. I think this can be improved with configuration changes, but that’s a whole different issue to look into :D Pulse is pretty well known for using a lot of CPU, even when idle. Ah I reckon the default stream settings in Pulse’s client config render the nf changes redundant, good spot! I might as well drop those extra steps.
0 Comments
Leave a Reply. |