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.
Teams has many greats features, but overall sluggishness (e.g. switching chat rooms) is killing. And that's on a powerful recent laptop. It's a drag to my workflow.
Murilo Maciel Curti commented
We really need an update here...
Brent Buchler commented
Is there any update at all on this item? Teams is practically unusable on a Surface Pro because of the memory consumption.
Pavol Donko commented
I need to kill Teams every 2-3 days because it eats gigabytes! of RAM on my Mac. It's continously growing on size. We use it actively in our company (around two hundred people). My coleagues said its the same on Win8/10.
There is also big difference between used memory and real (compressed) memory usage, but still every time I kill it my computer sudenly gain 5-6GB more of free RAM.
My project is using MS TEAM but its utlisizing more than 350MB of RAM and making the workstation slow. Our project uses Windows 7 and Windows 10 and processor ranges from Intel Dual Core, i3 and i7 but generally, all are frustrated with the memory usage and slowness its create to the machine and causing not to use TEAM!
When does Microsoft plan to have some fixes in place for this? And what is the recommended configuration for running Teams on Windows and Apple computers? We are in the process of piloting Teams for our organization, and want to be sure we are not causing resource problems for other memory-intensive applications, appreciate any guidance you can provide.
Need to dramatically reduce Teams CPU usage, it caused computers to crash, and users to not use Teams because it slows their PCs and cause other applications to crash.
Andreas Grip commented
I agree, it takes several seconds to move between diffrent places.
The feeling is that the product have to make some heavy communication (like soap rather then json) in order to get data from where you going, rather then keeping and subscribing to the information from all available channels. It's not like we need to keep everything, the last 100line + 100line before and after whereever focus is on that tab. (files/images and older history can be loaded on demand).
Stephen Nix commented
Any update on this? UI performance isn't great compared to Slack and 5 processes running?
Come on now...
PS C:\WINDOWS\system32> get-process teams
Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
337 23 35404 1992 0.55 3552 7 Teams
363 23 59880 17992 21.66 45060 7 Teams
362 25 37264 14012 0.69 98896 7 Teams
1079 98 293424 219412 272.20 142548 7 Teams
1177 60 72768 72860 64.83 143728 7 Teams
Philip Hendry commented
Teams.exe continuously uses 4-10% CPU with no Teams windows open at all. What's it doing (apart from stealing CPU from my other apps and draining my battery :( )
Any ETA? Took a quick gander at my usage. Why is there 5 different processes running for Teams?!?!
I thought it was an undocumented feature promoting thoughtfulness in posting, allowing you 2-3 seconds before slamming down another response in another channel and giving you time to compose your thoughts for the next flame war. :)
Any update on this? I really want to role this out in our organization but have to wait for the performance issues to be worked out.
Hariharan R commented
MS Teams currently slower in terms of start-up, restarts, logouts often, slow call establishment compared to other tools. Needs improvement on the performance and stability part of it.
Is there a status on this? Also experiencing extreme slowness when using the client, we have had to revert several of our users back to Skype for Business as a workaround because their systems kept crashing/freezing.
This is really slowing machines down. We cannot deploy Teams for multiple reasons and this is top of list. Please ETA??
ETA for this? Current memory usage is unacceptable.
Has this issue been taken care of ? We are running a pilot and experiencing a lot of memory utilisation issues.
Patrick Laramée commented
The ram utilization is out of control, http://imgur.com/a/Q2Seh
I had the application running for 7h and the computer is shutdown daily...
We tested Teams but cannot deploy. The switching between between chats is painfully slow. I prefer not to spend the $ for Slack but that may be the way to go if this basis GUI slowness doesn't go away soon.