5 ms·

Yeah ... I can run Discord, Zoom, Meet - anything really, and my system doesn't have any performance problems. I open up Teams and usage jumps to 100% (MBP 13"

Yeah ... I can run Discord, Zoom, Meet - anything really, and my system doesn't have any performance problems. I open up Teams and usage jumps to 100% (MBP 13" i7 2016)

alkonaut 6y ago
Have you reported this? I have never noticed it take something other than 0-1% cpu unless I'm actually doing something interactive like being on a call. I'm sure there are tons of bugs that cause this (which is bad) but that's different and much better to it being something inherent in how the App works.
- dijit 6y ago
  I guess this largely depends on what platform you're on or if you take meetings. My Linux and MacOS machines behave exactly as the parent suggests, it completely melts my laptops (and my laptops are not slouchy, i7-2020 MBP and a Precision 5520 with a Xeon E3-1505m). In fact, it's often the case that after a meeting teams will continue using 100% of a CPU core until it's restarted. Perhaps it's better in Windows?
  - alkonaut 6y ago
    CPU usage on windows isn't a problem as far as I have heard. RAM usage is, with 0.5-1Gb being par for the course. That's no worse than Slack et.al though.
  - 5h 6y ago
    It seemed to struggle after a video call for me. I tried to persevere & took to restarting the native app after every call for a bit, however on Linux you can't screen-share a single application (only an entire desktop). Due to this, and as the notification system is designed by a sadist, I switched to using it in a browser, which unfortunately means you can only see one person at a time on calls for some reason. It is now not uncommon for me to join calls twice at once from browser/app each, and juggle audio/speaker/camera settings for a bit to do demo's, then killing the native app. I can at least get native notifications & not convert my PC to a space heater this way, but it's still pure bullshit. I had a brief hope when I found some reference to native notifications in a config file, but that was a dead end.
skc 6y ago
Maybe they fixed something because I'm currently in a training session with about 25 people with a bunch of breakout rooms and shared docs and CPU is hovering around the 3% mark (but we mandated that you only turn your video/mic on when speaking) and it's pretty snappy. Still a bit confusing trying to find things but to be fair I have the same issue with most of these platforms. I think this area will see an increasing amount of innovation and it's anybody's guess as to who will come out on top in the end.
- joshspankit 6y ago
  What’s your OS and CPU/GPU? Wouldn’t be unheard of for MS to heavily optimize for newer instruction sets
  - skc 6y ago
    Windows 10 on an i7 (Dell). It's a work machine.
C1sc0cat 6y ago
I am running teams now and all my other tools slack office atom git hub and cpu sitting at 10/11%.
deleted 6y ago
[deleted]
rjewell 6y ago
there is an unacknowledged but reported issue in macos related to the "new meeting" experience, which in most versions is disablable. there are also some common issues with specific gpus, but again no acknowledgement beyond a common help suggestion to disable "gpu acceleration". if you're stuck using it and struggling, see if you can find a setting to disable the new popout conversation/meeting experience.

Yeah ... I can run Discord, Zoom, Meet - anything really, and my system doesn't have any performance problems. I open up Teams and usage jumps to 100% (MBP 13" i7 2016)

alkonaut 6y ago

Have you reported this? I have never noticed it take something other than 0-1% cpu unless I'm actually doing something interactive like being on a call. I'm sure there are tons of bugs that cause this (which is bad) but that's different and much better to it being something inherent in how the App works.

dijit 6y ago
I guess this largely depends on what platform you're on or if you take meetings. My Linux and MacOS machines behave exactly as the parent suggests, it completely melts my laptops (and my laptops are not slouchy, i7-2020 MBP and a Precision 5520 with a Xeon E3-1505m). In fact, it's often the case that after a meeting teams will continue using 100% of a CPU core until it's restarted. Perhaps it's better in Windows?
- alkonaut 6y ago
  CPU usage on windows isn't a problem as far as I have heard. RAM usage is, with 0.5-1Gb being par for the course. That's no worse than Slack et.al though.
- 5h 6y ago
  It seemed to struggle after a video call for me. I tried to persevere & took to restarting the native app after every call for a bit, however on Linux you can't screen-share a single application (only an entire desktop). Due to this, and as the notification system is designed by a sadist, I switched to using it in a browser, which unfortunately means you can only see one person at a time on calls for some reason. It is now not uncommon for me to join calls twice at once from browser/app each, and juggle audio/speaker/camera settings for a bit to do demo's, then killing the native app. I can at least get native notifications & not convert my PC to a space heater this way, but it's still pure bullshit. I had a brief hope when I found some reference to native notifications in a config file, but that was a dead end.

skc 6y ago

Maybe they fixed something because I'm currently in a training session with about 25 people with a bunch of breakout rooms and shared docs and CPU is hovering around the 3% mark (but we mandated that you only turn your video/mic on when speaking) and it's pretty snappy. Still a bit confusing trying to find things but to be fair I have the same issue with most of these platforms. I think this area will see an increasing amount of innovation and it's anybody's guess as to who will come out on top in the end.

joshspankit 6y ago
What’s your OS and CPU/GPU? Wouldn’t be unheard of for MS to heavily optimize for newer instruction sets
- skc 6y ago
  Windows 10 on an i7 (Dell). It's a work machine.

C1sc0cat 6y ago

I am running teams now and all my other tools slack office atom git hub and cpu sitting at 10/11%.

deleted 6y ago

[deleted]

rjewell 6y ago

there is an unacknowledged but reported issue in macos related to the "new meeting" experience, which in most versions is disablable. there are also some common issues with specific gpus, but again no acknowledgement beyond a common help suggestion to disable "gpu acceleration". if you're stuck using it and struggling, see if you can find a setting to disable the new popout conversation/meeting experience.