Teams uses 600MB and is super slow!
Quotes from various users about memory usage and slow performance:
"Team is a memory hog! 100s MB! Slack is about 50."
"The memory consumption is over 300MB!!! This should be a priority."
"Just started evaluating teams, 500+ MB and 10-15% CPU. This is in a citrix VDI. Does teams use hardware rendering? If so is there a way to turn it off? I had to do this with the rest of Office."
"I dont understand why my Teams application only uses 70MB when other people in my organization are towards half a gig! What is causing this Teams?"
"Make it less CPU heavy, 20% CPU on switch tabs? Really?"
"See attached picture."
Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.
It's horror! Constant lags and terrible loading speeds within documents from sharepoint!! And this is ONLY in the teams app! Wheres that cloud focus now, efffing dang.
James Brooks commented
Teams is constantly using around 500MB of RAM and often a large percentage of processor cycles, even when it is minimized and I haven't even used it once in a given day. Uncool
Teams client consuming CPU even when doing nothing. Unmanageable. Tried all tips and tricks I have found, no help at all.
So um... it's normal for Teams to use 25% of my 8th gen i5 CPU along with 500MB+ RAM when I simply move the mouse OVER TOP of the application without clicking on anything?
Sorry Microsoft, but other Electron apps, like Discord and Slack, simply don't have this problem. It's good to hear more improvements are on the way, but as it stands, MS Teams is currently unusable in its' current form.
Currently editing documents in:
Adobe FrameMaker, memory usage: 65 MB
Microsoft Word with one document open, memory usage: 94 MB
Photoshop with two files open, memory usage: 43 MB
Slack, memory usage: 65 MB
Teams is running in the background but otherwise idle, memory usage: 271 MB... as much as all the others put together, and it's not "doing" anything!
There is clearly something very wrong with Teams.
Issue open since 2017 , MS isnt able to fix CPU/Memory consumption for such a ****** app ... Well done product group. But in the end with the product team it all ends as a feature or by design... so i guess it is by design.... If that designer works in my company i would kick him...
Another problem for battery is the usage of GPU. need to use Teams daily as work tool with a all day calls, this temporary solution of having the GPU disable also affects the possibility of sharing your screen. So meetings get cut over what you can do. Really annoying and unnecessary from the dev Team of Microsoft.
Attached an example when the GPU is disable, it will say you need permission but that's not the case.
Chad Wilson commented
I'm also seeing this. There seems to be a huge difference when I use my webcam. Resources go down when I turn webcam off...but I use a webcam 100% of the time in virtual meetings.
Manu E. commented
This one should really be on top of the list! Very annoying.
Stan A. commented
The Teams consume full core of processor and a lot of RAM after the windows start. It happen on all notebooks in our company. The processors temperature go up fast. But if we maximize the Teams window and click on any chat or team (or something) in that window so the Teams will stop to consume full core of the processor and everything go back to normal. Can you help to us? We use Win10 and Win7.
My wife's 2-year old Dell laptop has a lag time of about 2 minutes per mouse click, now that teams are in Windows 10. The disk activity is between 94 and 100 % for a long time, about 20 minutes. We are not even logging into Teams. If it was light-weight and fast we would. Fix this Microsoft. It has made a boat anchor out of her laptop.
Deleted from desktop. What a resource hog!
Web version is functional.
Yeah.. it is super slow especially in starting up. Many of my user remove the program and use email instead! That is insane. And those are top executive, cannot force them to put it back on. So our company stepped back 30 years because we don't allow other communication software!!! Please fix this long lag issue!!!!
Jose segura commented
I found some interesting information on a JAMF blog related to Teams and high CPU utilization that was really interesting. https://www.jamf.com/jamf-nation/discussions/31727/microsoft-teams-high-cpu-utilisation.
random n commented
The CPU usage seems to be particularly bad if Teams restarts itself for a silent update, or is started with "Open application in background" active and never brought to a visible state. From what I can see, the mainWindow renderer never pauses in this condition, and animations like the blinking text cursor (whose blink rate doesn't honour the system setting), the chat window updating, emojis, etc will still consume resources in the background unnecessarily.
Suppressing updates with hooks.json customization and preventing use of the --system-initiated parameter in the startup key (HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run\Teams) will help with this (and the former is necessary in a VDI install to stop repeated failed updates), but that's all a set of band-aids. It needs a proper fix from the Teams team.
So.... 3 years working on it?
How about info on what progress has been made, if any. We have some powerful computers in the office and this seems to be a real drag. I don't understand the CPU usage when the app is just idle. I found if I close and reopen it, the CPU drops but memory usages is still high.
Still slower than Skype and consumes more memory - this is not an upgrade!
Rafael Vilela commented
The company that I am working on is moving the Skyper for Business to Teams and I can say we are in a really complicated situation. I have 8GB RAM in my laptop an Teams is not stable (high CPU and memory usage), sometimes I click on Teams to reply a message and there is a delay (it is true) of about 10 SECONDS to open the window.
HOW CAN I WORK USING TEAMS?!