Additional features, settings, or issues not covered by specific Microsoft Teams categories
Great find! This actually did help reduce our CPU usage dramatically. However, it deserves a fix.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi
Teams is almost killing my laptop. Here's an example:
Is there anything can do to reduce Teams' memory usage?
Or do I just need to buy more memory?
Thanks!
Additional features, settings, or issues not covered by specific Microsoft Teams categories
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Great find! This actually did help reduce our CPU usage dramatically. However, it deserves a fix.
We found the culprit to be the Teams Add in for Outlook. When we unticked it, performance went back to normal. This was a Win210 machine running 1909 Office Apps.
They really need to fix this as whats the point of teams if we have to remove it from outlook
Am I the only one that did this and now it hogs *more* memory?
I also tried disabling GPU hardware acceleration and disabling the Teams add-in Outlook and no dice. :(
Do they just have a way to delete old conversations? Maybe I'm just blind, but if the option is there, I can't find it. Perhaps that might help a bit?
It's not always an issue, but at times it's slowed everything to a screeching halt and I've had to completely turn it off to get anything done.
@Microsoft, Teams dev team - can we consider this to be a memory leak (security issue)? I see my CPU (8th gen i7 w/8 cores) is running about 30% CPU all the time when Teams is just sitting in the background. This just started recently, presumably after some kind of update or after the message DB grew beyond a certain size? Is it possible to have corruption in the database files?
It really is liking the resources though because I changed process priority to real-time (24) it begins to be more responsive - there are still delays but they are only 1-2 seconds as opposed to the typical 5-10 second delays before text appears that I just typed, or my mouse cursor stops being frozen, etc.
I hope that you are able to turn things around with this application...it has really taken a downward dive here with the resource problem but I'm sure it's a top priority and being worked on, given the amount of time gone by here though it must be difficult to fix. I'm looking closely at what's happening in Process Explorer (https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer) as well. If any details would be helpful for Microsoft resolving this issue, please let me know and I will provide them.
This might sound crazy, but how about no new features (that add to the problem) until this is resolved? Teams shouldn't be taking up vastly more RAM than Slack or Outlook.