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.
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).
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?
Cory Wagner commented
I have to agree about the RAM and CPU consumption. It's especially bad when using the video functionality. The other day, it pegged my processor for the entirety of the meeting, and it used over 500MB of RAM. I had to close everything else to make it usable.
Jean BLANC commented
Teams is really slow to open on every PC in my organisation.
The main problem is also the usage of RAM the app requires : more than 300Mo of RAM (shared between all the processes) when the app is not even used.
On computers with 4Go of RAM (or even less sometimes) this is a big problem for the final users because the performances of other programs drops because of the lack of RAM.
it's slow comparing to Slack. I can't navigate between chats smoothly
Teams is performing a little "laggy" since the general release last week.
Murilo Maciel Curti commented
I have the same usage as @HH reported.
I'm using Windows 10 Pro x64
@HH - Is this Windows 8.1 or 10? With Windows 10 I don't see it more than 50MB, however with Windows 8.1 I clocked 785.9MB and can easily reproduce the memory issues over again..
Only 100? Teams is currently at 950MB RAM usage on my system.
True..On my system it regularly uses up 200-350MB memory ..
Jason Mayde commented
We are seeing this as well with the latest 1.0.00.6201 release on Mac and PC.
The loading time for the Chat & Teams is over 1000ms.
For different views in an application I would expect the loading time to be <100ms.
See this article on usability: