6 ms·

Off topic: I wish someone would do this kind of analysis to determine why Microsoft Teams helper process is always at 50-70% CPU load on my M-Based MacBook Pro.

Off topic: I wish someone would do this kind of analysis to determine why Microsoft Teams helper process is always at 50-70% CPU load on my M-Based MacBook Pro. My laptop is warm/hot to touch as a result of it.

deleted 3y ago
[deleted]
ThePowerOfFuet 3y ago
Because Teams, and also because Electron.
- dmd 3y ago
  That’s essentially a circular argument. “Teams is bad because it’s slow. It’s slow because it’s Teams.”
  - worewood 3y ago
    As a Teams user on the crappy PCs the company gives, this is an argument I can get behind. It looks circular but there are implicit meanings hidden there: "Teams is bad (not only) because it’s slow. It’s slow because it’s Teams. (as in, Teams has a looong list of defects, slowness just icing on the cake)”
    - dmd 3y ago
      Yeah fair.
dangus 3y ago
I’m not experiencing that issue. Have you tried completely uninstalling it and reinstalling?
- alberth 3y ago
  I never had this issue when running the Apple Silicon Microsoft Teams version. It actually was quite good, contrary to what most would say. But after receiving the push update converting Team to using the Electron version of the app, CPU load dramatically increased. Wish I could convert back to the older Apple Silicon non-Electron version.
  - fingerlocks 3y ago
    They’ve all been electron based. The only meaningful change was the arm64 builds that came out last year.
    - dangus 3y ago
      I just wish people would stop blaming Electron for everything. Teams isn’t a buggier, worse performer than VSCode or Slack because of Electron.
pjmlp 3y ago
Best way to use Electron stuff, is via the Web app.
wasyl 3y ago
I wish someone did an analysis to determine why my intel-based macbook is so incredibly laggy all the time, even after fresh system installation. I can't shake the feeling that Apple Silicon is so much faster that performance issues just got into the system without anyone at Apple bothering to fix them, and Intel macs suffer as a result.
- rspoerri 3y ago
  It's overheating and the (my) problems came from: - loading the battery and powering the device - high gpu power usage when plugging in a external monitor - cpu power usage - bad cooling which must be cleaned often My recommendations: Plug in the power from the right side. Afaik the thermal throttling kicks in sooner if you have it plugged in on the left. Clean the device. Unfortunately it really sucks to open it. You will need special tools and lots of trust in the spaghetti monster that you dont break anything. Cpu power usage can be lowered by using any of the tools: https://github.com/sicreative/VoltageShift https://github.com/sicreative/VoltageShift https://volta.garymathews.com/ https://volta.garymathews.com/ (most probably not working anymore) Unfortunately in later updates apple prevented undervolting the cpu so it's (VoltageShift) use is limited now. But i was able to limit the power usage to 5W, which somehow helped keeping my device cooler. Be aware that you need to disable quite a lot of security measures to install Voltageshift. Apparently having power saving active even when plugged in helps keeping the cpu and gpu cooler. I did not test this extensively because i switched to a m2. A big problem comes from the gpu, if you have an external monitor plugged in, the video drivers start using 10W+ which causes problems when you are loading the battery as well. There are a lot of discussions on what causes the problems, it has to do with the drivers and some screens causing it to use way more power then needed. It can help to close the lid of the macbook while working with a external monitor.
  - wasyl 3y ago
    Thanks for the suggestions, this all sounds plausible, however: - I routinely clean, or at least de-dust everything accessible after removing back cover - the lag is there always, even right after resuming the mac, before any thermal throttling should be kicking in. I also don't observe throttling with `pmset -g thermlog` - I'm not using an external monitor At this point the most likely culprit is the battery, mine is at 789 cycles although the condition is reported as "normal". I wish it were possible to confirm whether battery is an issue before spending couple hundred $ on replacement though

deleted 3y ago

[deleted]

ThePowerOfFuet 3y ago

Because Teams, and also because Electron.

dmd 3y ago
That’s essentially a circular argument. “Teams is bad because it’s slow. It’s slow because it’s Teams.”
- worewood 3y ago
  As a Teams user on the crappy PCs the company gives, this is an argument I can get behind. It looks circular but there are implicit meanings hidden there: "Teams is bad (not only) because it’s slow. It’s slow because it’s Teams. (as in, Teams has a looong list of defects, slowness just icing on the cake)”
  - dmd 3y ago
    Yeah fair.

dangus 3y ago

I’m not experiencing that issue. Have you tried completely uninstalling it and reinstalling?

alberth 3y ago
I never had this issue when running the Apple Silicon Microsoft Teams version. It actually was quite good, contrary to what most would say. But after receiving the push update converting Team to using the Electron version of the app, CPU load dramatically increased. Wish I could convert back to the older Apple Silicon non-Electron version.
- fingerlocks 3y ago
  They’ve all been electron based. The only meaningful change was the arm64 builds that came out last year.
  - dangus 3y ago
    I just wish people would stop blaming Electron for everything. Teams isn’t a buggier, worse performer than VSCode or Slack because of Electron.

pjmlp 3y ago

Best way to use Electron stuff, is via the Web app.

wasyl 3y ago

I wish someone did an analysis to determine why my intel-based macbook is so incredibly laggy all the time, even after fresh system installation. I can't shake the feeling that Apple Silicon is so much faster that performance issues just got into the system without anyone at Apple bothering to fix them, and Intel macs suffer as a result.

rspoerri 3y ago
It's overheating and the (my) problems came from: - loading the battery and powering the device - high gpu power usage when plugging in a external monitor - cpu power usage - bad cooling which must be cleaned often My recommendations: Plug in the power from the right side. Afaik the thermal throttling kicks in sooner if you have it plugged in on the left. Clean the device. Unfortunately it really sucks to open it. You will need special tools and lots of trust in the spaghetti monster that you dont break anything. Cpu power usage can be lowered by using any of the tools: https://github.com/sicreative/VoltageShift https://github.com/sicreative/VoltageShift https://volta.garymathews.com/ https://volta.garymathews.com/ (most probably not working anymore) Unfortunately in later updates apple prevented undervolting the cpu so it's (VoltageShift) use is limited now. But i was able to limit the power usage to 5W, which somehow helped keeping my device cooler. Be aware that you need to disable quite a lot of security measures to install Voltageshift. Apparently having power saving active even when plugged in helps keeping the cpu and gpu cooler. I did not test this extensively because i switched to a m2. A big problem comes from the gpu, if you have an external monitor plugged in, the video drivers start using 10W+ which causes problems when you are loading the battery as well. There are a lot of discussions on what causes the problems, it has to do with the drivers and some screens causing it to use way more power then needed. It can help to close the lid of the macbook while working with a external monitor.
- wasyl 3y ago
  Thanks for the suggestions, this all sounds plausible, however: - I routinely clean, or at least de-dust everything accessible after removing back cover - the lag is there always, even right after resuming the mac, before any thermal throttling should be kicking in. I also don't observe throttling with `pmset -g thermlog` - I'm not using an external monitor At this point the most likely culprit is the battery, mine is at 789 cycles although the condition is reported as "normal". I wish it were possible to confirm whether battery is an issue before spending couple hundred $ on replacement though