Poor performance on Windows
The system takes a lot of the computer resources and slows down the overall performance of the pc
We are happy to share that Electron 10 is rolling out to the public ring now, so you should notice improvements. We expect overall performance of Teams to improve even further with upcoming fixes around the calling and meeting features We will share another update as soon as we are able to.
Agree with Gordon - it's general UI responsiveness, not so much hogging resources and slowing down the pc. The whole app is incredibly sluggish, click, wait, click, wait, click, wait...
Gordon Tyler commented
General UI responsiveness is my main irritation.
- Clicking the Reply button below a conversation takes far too long before I can actually type.
- Clicking between Teams and Chat on the sidebar takes far too long before it actually displays the new view.
- When in a meeting, the main Teams window becomes even more unresponsive than before.
Stop adding features. Focus on the core user experience. Make it snappy!!!
Rafael Schiavoni commented
Maybe this is by design. On a teams meeting, you pc should be dedicated to that meeting window, or are you multitasking???
Thomas Kristensen commented
Teams consumes 10-15 times more ressources than Zoom - making it practically impossible to work in other apps (even in the Office suite)
Ryan Spooner commented
The app is overly slow on Windows, which is probably due to the huge amounts of resources it consumes. During a Teams meeting with screen sharing and several participants, RAM usage can balloon to nearly 1.5GB of memory usage, and you often see the whole CPU pegged at 100%, though task manager does seem to only show Teams using around 30% at that time. Still, 30% constantly is huge and is excessive when compared to similar services from other vendors.
Maxime Ouellet commented
MS Teams actually consuming x6 upper than Webex Teams, and x10 upper than Jabber on my thinkpad T490
MS Teams = 544.8Mb(11.6%CPU)
WebEx Teams = 84.1MB(1.6%CPU)
Cisco Jabber= 59.9MB(0.2%CPU)
and if i start a Visio meeting, MS Teams goes more than 1Go (21.6%CPU), Jabber only 117MB (1.6%CPU)and WebEx Teams 161,7 MB (4.2%CPU)
Also when not on a conference it is slow without doing anything. It just crawls.
When video is on, it takes ~2 minutes before it even displays the screen/app list for sharing. Then everything slows to a crawl, making presenting ponderously slow. This is on a 16 GB/i5-8350U/NVMe laptop, Win10 20H2.
Zoom is much faster when trying to do the same.
Using Electron is an insult to desktop users. Please ask WPF, UWP, QT, or Xamarin developers how to build apps for Windows and Mac. Or ask Telegram for advice on how to develop a communications app. You will have a lot of graeful users instead of annoyed ones ("Thank you for not writing in Electron" https://github.com/telegramdesktop/tdesktop/issues/6290 ).
Many seconds to show the calendar is ridiculous. How can it be useable on a phone and yet hopeless on a reasonably fast PC?
Timothy Carroll commented
Slack runs on Electron, which is built on Chromium, which is a MASSIVE resource hog, yet it runs circles around Teams in terms of performance. Team is an embarrassment when it comes to performance.
Renz Marty commented
Slow Performance of MS Teams on phone.
Way too slow for a productivity product.
When...oh when...oh when...will the performance issues with Teams be sorted? In particular Shifts...abominable...and the rest of the app when you're in a video call...btw Zoom doesn;t seem to suffer from this
Slow and teams window crashes or vanish from the screen resulting in system reboot
Throw away electron and build a native, fast 64bit windows 10 application already!!! This thing literally crawls...
The MS Teams search process so slow it kills me to search any keywords from previous chats. It hangs MS Teams momentarily. This is across all our company users, not just me,
Roberto Fasiani commented
Teams is killing almost all Windows PCs in our organization. While in a Teams video meeting, even on fast machines wtih 16Gb+ memory, everyone complains the system becomes slow and unresponsive.
The application should be entirely rewritten using some lighter framework.