Forum Discussion
Teams Performance
😉
Sure, try telling this to anyone running Teams on a laptop/netbook with 4GB RAM 🙂
- Oct 09, 2019I mean I guess technically in that case if you run out of memory, then Memory usage = performance lol :). I remember it used to use like 1.2GB or something crazy, I don't usually see it going much over 750MB these days, it def. can still use some tweaking which I'm sure will continue to improve over time.
- kirashiMar 05, 2020Iron Contributor
ChrisWebbTech it still regularly uses 1.5GB RAM and over 30% CPU during meetings, slowing our 8th Gen Intel i5 CPU 8GB RAM HP EliteDesk G4 Mini PCs to a crawl when users have so much as 5 Chrome tabs, the Outlook 365 Desktop app, the OneNote UWP App, and the Microsoft To-Do app open.
Normally I would agree that memory usage != performance issues, however, when your machines have to split available RAM between the integrated graphics and other mandatory company programs, it's hardly acceptable to see Teams using 20% of the total available, especially when other apps built on the same ElectronJS platform (Discord & Slack, for example) manage to consume almost nothing during a call or when switching text channels.
When I use MS Teams to join meetings from my home computer with a 4th Gen i7 and 24GB RAM, it still chugs while utilizing the same resources, albeit a tad less CPU. To be clear, my home PC is able to switch to other applications a little faster, but the extra RAM and processing power don't seem to help Teams performance at all, indicating a problem with the code that makes up Teams' core.
I understand development takes time, but it's going on 6+ years now with Teams still exhibiting performance issues. Maybe it's time for a rewrite of Teams from the ground up similarly to Slack's recent rewrite?
- https://microsoftteams.uservoice.com/forums/555103-public/suggestions/17219609-teams-uses-600mb-and-is-super-slow
- https://www.infoq.com/news/2019/07/slack-desktop-successful-rewrite/
- https://slack.engineering/rebuilding-slack-on-the-desktop-308d6fe94ae4
Tagging jcgonzalezmartin and jimharpert so they can see Teams using more than 1GB RAM at least once in their life. Also looping in VasilMichev and Eric DeVaudreuil because they're spot on with their prior comments about high resource usage. Also making StevenC365 aware of why one might not want to see a single application utilize such high amounts of resources.
- VasilMichevMar 05, 2020MVP
It's a lost cause mate, that's how "modern" development works.
- jimharpertJan 14, 2020Copper Contributor
ChrisWebbTech Thanks. I agree memory is not exceeding ~800mb lately. Maybe some update fixed this 🙂
On the other hand, my CPU spikes were still dramatic. I fixed this by disabling the GPU rendering in Teams (strange? I would say GPU rendering should improve the performance instead of degrading).
See https://www.itexperience.net/2020/01/10/fix-performance-issues-teams-high-cpu-memory-usage/
He also speaks about disabling the Outlook add-ins and integration, but actually I want to keep those features. I'm happy with the performance for now.
- StevenC365Jan 14, 2020MVP
jimharpert why wouldn't you want it to use as much CPU as possible when it has something to do? Surely it should just do things as fast as possible and then be done.
- Dustin_HalvorsonOct 15, 2019Steel Contributor
ChrisWebbTech Yet the minimum requirements still say 2GB! That's unrealistic.
In an organization that wants to move to Teams that has spinning disks, and 4GB of RAM in desktops, it's a product that is impossible to support.
It's frustrating to see the team continuing to post on things like integrations with third parties, when the core of the product is still extremely inefficient, and there doesn't look to be any priority put towards it.
- Oct 15, 2019To be fair, I have never seen Teams Desktop client using 1 GB neither 2 GB ofr RAM memory