Client high CPU usage #1194

New issue

Closed

opened 2026-02-20 20:03:30 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-20 20:03:30 -05:00

Owner

Originally created by @Avamander on GitHub (Apr 20, 2017).

Version: 1.3.0~2310~g9e834cb~snapshot-1~ppa1~yakkety1
OS: Ubuntu 16.10

I have noticed that when Mumble is connected to the server and even when there's no voice being transmitted (push-to-talk) and no one is speaking, it's utilising about 10% of my CPU, that'd a tad high. When there are other people speaking it rises to about 13%.

Originally created by @Avamander on GitHub (Apr 20, 2017). Version: 1.3.0\~2310\~g9e834cb\~snapshot-1\~ppa1\~yakkety1 OS: Ubuntu 16.10 I have noticed that when Mumble is connected to the server and even when there's no voice being transmitted (push-to-talk) and no one is speaking, it's utilising about 10% of my CPU, that'd a tad high. When there are other people speaking it rises to about 13%.

deekerman

2026-02-20 20:03:30 -05:00

closed this issue
added the
client

priority/P2 - Important
labels

deekerman commented

2026-02-20 20:03:33 -05:00

Author

Owner

@mkrautz commented on GitHub (Apr 21, 2017):

This is a long standing issue.

Mumble, on all OSes, will keep recording input and feeding it to the preprocessor pipeline, in order to make the automatic gain control, work well, among other things...

When using the PulseAudio backend, Mumble can use quite a bit of CPU when doing this. I believe the other backends are a little better in that regard.

There are other issues, someone should probably merge this into them.

@mkrautz commented on GitHub (Apr 21, 2017): This is a long standing issue. Mumble, on all OSes, will keep recording input and feeding it to the preprocessor pipeline, in order to make the automatic gain control, work well, among other things... When using the PulseAudio backend, Mumble can use quite a bit of CPU when doing this. I believe the other backends are a little better in that regard. There are other issues, someone should probably merge this into them.

deekerman commented

2026-02-20 20:03:33 -05:00

Author

Owner

@Avamander commented on GitHub (Apr 22, 2017):

Though would it be possible to stop the input recording, it shouldn't affect much when push-to-talk is used and/or when mic is muted, to just not waste CPU?

@Avamander commented on GitHub (Apr 22, 2017): Though would it be possible to stop the input recording, it shouldn't affect much when push-to-talk is used and/or when mic is muted, to just not waste CPU?

deekerman commented

2026-02-20 20:03:34 -05:00

Author

Owner

@Kissaki commented on GitHub (Apr 22, 2017):

It’s so sound/volume amplification and noise suppression or whatnot works as intended when you do press the PTT. It has been discussed in the other issue tickets. #1092

@Kissaki commented on GitHub (Apr 22, 2017): It’s so sound/volume amplification and noise suppression or whatnot works as intended when you do press the PTT. It has been discussed in the other issue tickets. #1092

deekerman commented

2026-02-20 20:03:34 -05:00

Author

Owner

@Avamander commented on GitHub (Apr 22, 2017):

Okay, but at least when the mic is muted then it shouldn't listen.

@Avamander commented on GitHub (Apr 22, 2017): Okay, but at least when the mic is muted then it shouldn't listen.

deekerman commented

2026-02-20 20:03:34 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Dec 3, 2017):