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.
Juan Congosto commented
The entire Teams concept is wrong.
We don't need one fat, slow and buggy piece of software to get in the way of every possible action in our daily workflows. We need small, responsive and stable utilities that do their job right and that can communicate with other through APIs.
To switch from my calendar to a chat should only require hitting alt-tab, not a click and several seconds of delay while a.- the context I was working on in my calendar is lost and b.- the chat context is loaded from scratch.
It's as if, to compare two documents, you had to close one, open the second one and scroll to the relevant part... every time.
For decades, Microsoft has worked on Windows to allow us to multitask, to have multiple open applications and to quickly switch from one to the other without altering their state in the process.
Now we are forced to go back to a working model more in line with single-user, single-task MS DOS.
[Deleted User] commented
Version 1.3.00.13565 just released, where can we find the release notes?
Overall app performance needs to be improved so that it's in line with other video conferencing applications that offer similar functionality. Switching windows within Teams can sometimes be slow. What I've noticed is that if you Spotlight / Pin the video to a single user, the performance improves.
After a meeting it occupied 980MB -- I mean 980MB even after the meeting had ended. How can it be like this? Skype for Business only takes less than 100MB to run.
Apparently you are making the memory usage scale according to Moore's law while the hardware is not scaling any more.
I am experiencing a lot of issues with Teams, sometime Teams freezes my PC completely and I have to restart, it happened a few times when I am in the meeting on Team. I see that it is using more than 800 MBs on my system
Check the below Screenshot:
This is really a big hassle when all the contacts are happening online.
I hope you are able to resolve it soon. :(
Jasen Webster commented
I am waiting for this to be fixed. Teams eats up to 600MB of memory. This is a lot when you only have 8GB to run everything. Continues to cause Outlook to not be able to open other folders due to low memory. If I kill Teams, everything runs great and my battery life lasts much longer. At least give me the ability to restrict how much memory Teams can use.
Running at over 600mb for just sitting there, what's its really doing to be taking up that amount of memory? No fix and no answers from Microsoft.
IT dude commented
not only this takes 300-400 MB of RAM, in our terminal servers environment it turns our the process takes around 400MB PER USER!! multiple it by 10 users (which is fairly common usage for a terminal server) and you got 4GB of RAM wasted on this....
i would says it acts like a malware considering the fact 90% of us didnt even wanted teams (it was forcefully pushed in an Office 365 update).
The desktop app is nearly unusable. It takes a full minute to see any characters that I type.
Indicative of a mobile first design - build app first - barely fix issues for 3 years - remove app from store - replace with new app with mostly the same problems.
Not recommending this, 99% of my corp's thousands of users use Teams on a laptop and not on mobile.
Microsoft, remove unused features down to just text chat, post image in chat, audio call, video call. no need for integration with calendar and other applications and never a replacement for a stand-alone Outlook email client.
Wasn't Outlook + Skype promised to be made into a unified in-box 5 years ago?
- Basic text chat
- Post basic images in chat
- Voice call
- Voice call with screen share
- Text + basic image posted in a channel
- Video call much less important
- Like emoji
- Animated GIF responses
- Triggers with other apps such as "A new job request has entered the ABC queue" messages repeated in a channel
- Email informing me someone posted in a channel
- Integration with Outlook inbox and calendar
- Showing a person's picture next to each person's message in a channel
- Copying cute stuff that Slack or older HipChat had
- File storage for a channel. Just have a list of channel links with one being a Sharepoint site
- Video files in the channel
- Voice messages in the channel
- Recording of meetings
- File attachments in the channel or chat messages
- Real time text transcription of voice calls and meeting audio
Recommend that IT buyers evaluate the installation image of software like Microsoft Teams to determine if the app is written in a sustainable technology set.
My IT shop does this does this today to determine if the app is using very outdated third party add in code modules.
I did this in the mid 2000s to find out if the application had holdover code modules from the mid 1990s Windows 95/98/me era.
We do not adopt applications using niche third party code modules without careful extra vetting.
For enterprise class productivity software, support costs are everything.
A forced upgrade or forced move to another software for my company's thousand of desktops plus mobile devices costs us tens of thousands of dollars and increased support costs.
Teams with its poor technology set, as pointed out by others here, is to be avoided.
99% of our users use Teams exclusively on laptops and not on mobile devices.
Still waiting for this... This sucks! I'm going to advocate my company of 500+ stop using Teams because it's such a resource hog. It's a terrible user experience.
I even turned ON [x] Disable GPU hardware acceleration, which is recommended by some, and also Read Receipts... This helps a little (goes from needing 90%-105% CPU & RAM down to 'only' needing 80%)...
Ferb! I know what the Microsoft Teams team is going to do today!
- not happy with MS Teams and actively advocating my company stops recommending/requiring it.
The memory usage is due to a programming language + programming library used by Teams.
Only a rewrite in a different technology stack or drastic reduction in features will reduce Teams memory usage.
React Native is good for small applications with 2 to 3 screens and simple logic; bad, unusable and unsupportable for larger complex apps.
The mobile app model for 95% of apps is to build the app in whatever technology is trendy at the time, make minor updates but no major changes, then dispose of the app in less than 3 years.
Repeat the process with the new technology 2 years after the first app was released using whatever is the trendy technology.
Teams is a ridiculous memory hog. Why does it need half a gig? to do, what exactly?? other than slow everything else down. If I didn't have to use it for work I'd have deleted it by now
Philip Leitch commented
4 years later and still waiting.....
John Hardwick commented
The number of times on a daily basis that I hear from my team complaining about Teams slowness is incredible.
For consumer software outside of Office and Outlook, Microsoft typically releases a new replacement product every 6 years.
By the time the existing product has critical mass of users and blocking bugs, the next new replacement product is due in 2 years.
Hence, no reason to make big changes to the existing product and "we are customer focused on improvements and usability" deferral comments from the MS support group.
2011 - Microsoft bought Skype in 2011.
2017 - Teams was released in 2017 - 6 years later.
So does that mean Teams replacement due in 3 years in 2023?
This happens with other MS products that 'wait until the next product in about 2 years, it will fix your issues....' is the mantra
Luis Muñoz commented
How come my computer can run finite element analysis software and CAD software at the same time, but open Teams and it brings it to its knees? Is there a fix on the way? Should the whole company switch back to Cisco solutions, or even worse, Skype?
Pablo Estigarribia commented
New with new chat Pop up, every new chat windows uses 100 or 200mb more.
So you can have a Teams processes with up to 2Gb of RAM usage if you have lot of chat windows.
Seems that performance was not prioritized for this new feature.
Over 3 years and 11K votes later and all we get is "Great performance and user experience remain a topmost priority". As far as I can see there are two possible conclusions here. Either that statement is true, but the people working on this project are not anywhere near competent enough to actually make something happen, or it's just an outright lie and we are simply being ignored. Or both...
Either way, I'd advise anyone to stay away from Teams when possible. Pick any alternative product at random and it will be better.