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."
Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.
Definitely still a resource hog. :(
I'm seeing this same issue on VMWare Fusion. I have 4 vCPUs assigned to the guest. It only pegs things when the Teams client is in the foreground. If I minimize it to the tray, CPU usage drops to normal. This happens even when Teams is the only app open.
Teams finally broke the 1GB mark for me yesterday.
WOW. So this is where we have come. Microsoft using Electron to save money and push a cross-platform application too soon that performs horribly on their OWN operating system.
How is it that Teams uses more RAM and CPU than VISUAL STUDIO on windows? Who let this happen? Why can you not develop native for each OS and have a performant app?
The file upload speed when sharing (drag/dropping) is absolutely abysmal. Took me 10s to upload a 23KB file on a 100mbit upload speed connection.
Rick Ross commented
On my 2016 MacBook, Microsoft Teams is using a substantial amount of memory at 181 Megs, but Microsoft Teams Helper is using over 680 Megs!?
What is this Microsoft Teams Helper and how is it helping me? This is way too much combined ram usage between these two processes, and it feels like there's room to reduce this by quite a lot. Competitive clients do not use this much ram on my machine.
Finish the development and perform some probing before release!
Nick Folkmann commented
As we have been testing we also see that when on a call teams has two processes running and it each process can take up to 30% of the processor each. The CEO here has seen it when using his surface pro 4. He stated when he is on a call it take so much of his processor that when trying to use other programs, it makes everything lag. This is deterring him from wanting to switch to teams as are only communication tool. He said he has seen the same behavior when using the free version of skype.
Rowland Shaw commented
Currently, it seems the client allocates ~0.1Mb a second, even when idle, with the activity tab open (seems to be worse when the activity tab is open).
Maximilian Klingelhöfer commented
This should indeed be removed since it doesn't suit any purpose at all...
[Deleted User] commented
Only 15 Votes? This has to be fixed asap
On a Mac Teams uses the dedicated graphics card, although I'm not sure why. Would like to see this looked at as well.
Glynn Lloyd commented
Only been using it for a few weeks with 3 users to test it and already it's using 175MB RAM and often causes the computer to crawl.
It is true, especially the more messages and teams we create.
Govardhan Reddy commented
We are using Teams on Production . 500+ employees using teams. Only the complaint we are receiving from the stack holders is Memory utilization.
Current Memory utilization is 500 MB on windows machines. Can you please update me the status when this issue get resolved.
Teams is very slow to switch between items, type on threaded conversations, pretty much do about anything on a really advanced, modern computer.
Rowland Banks commented
I eventually tracked the issue down. The user only had 1 vCPU assigned to their machine. Assigning additional CPUs fixed it. Weirdly they had been running for a year like this, with no other problems!
Rowland Banks commented
All our employees use Macbooks. If they install the Mac version of Teams on Mac OS X, or install Windows natively (via Bootcamp) and install the Windows version of Teams, then performance is absolutely fine.
However, if they install it into Windows 10 running as a Parallels VM, it uses 100% CPU, and slows the machine to a crawl.
This is readily reproducible, and I am happy to supply additional information if required - I have attached the OS and Parallels version information.
32-bit version of Office 2016 is installed by default, even on 64-bit Windows operating systems. What is recommended for Microsoft Teams?