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.
I can also speak to this, we have several workstations stuck on 32 bit until I can upgrade them to Windows 10 Enterprise 64 bit later this year. (Some are on Win7 64 though) We are also seeing memory issues on several workstations where MS Teams is basically locking up the computer and causing crashes.
Sad because we actually want to use MS Teams for our entire office and scrap Skype for Business/installs of Slack. More of my concern is that we are also seeing this RAM hogging on new computers running Win7 64 bit and 8GB of RAM. When the system is locking up multiple times a day its a real productivity killer. Please fix this.
Christopher Roberts commented
Mine is also using just under 1GB of ram, not good considering it's my development machine..
Peter Kondrashov commented
Teams constantly takes anywhere from 0.5 to 1.5 seconds to load news screens when switching chats/teams. Please make it snappy like Slack. Its seems like a small difference but it's what determines whether the user experience is pleasant or not.
Rob Chalmers commented
upload speed is slow - way slower than Slack and we have 100MB fiber upload
It's just a webapp. So they can add features rapidly but the foundations are bad. Perhaps they could fork the UWP version? Is that a native app?
Slack is not so great either. It is fast (also a webapp but remarkably fast) but just open task manager and see the number of processes it spawns. For such a simple app.
I find it incredibly slow. I am in Asia and it feels like every keystroke is travelling to MS HQ and back... Please improve the performance!
Using Win 8.1 Enterprise and also have performance issues. It doesn't use much of RAM, but is just slow...
Greg Wellman commented
Just installed Teams yesterday, and it's consuming 1.3 GB RAM. Unacceptable for what ought to be a lightweight application.
Josue Mendizabal commented
Hello, any improvement about this?
As everyone the desktop client is in the top of usage 350Mb, higher than outlook (110Mb) and chrome (135mb). I'm using Win 7 Enterprise, Lenovo ThinkPad 430
I am waiting to role this out in my company as some test users are experiencing 150-300MB but others are at 30-50MB. Any word when improvements will be made?
Jay G commented
New Mac build Microsoft Teams Version 1.0.00.9502. appears to have a slow memory leak and is worse than build before it. At around 300MB after a restart but climbs to over 800MB in little more than hour.
Govardhan Reddy commented
Can we have a ETA on this?. Our company is already using teams and teams is very slow and feels lagging all the time. Is there hope that this will be better sometimes?
If you switch between Team Channels f.e you have to WAIT a Second and sometimes more...
Make it like google chat - one window on the right side that takes minimum space This one takes too much of CPU power. Unusable in the current form
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!