Teams Performance

%3CLINGO-SUB%20id%3D%22lingo-sub-898206%22%20slang%3D%22en-US%22%3ETeams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-898206%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20anyone%20from%20the%20Teams%20product%20group%20offer%20an%20update%20on%20performance%20of%20the%20windows%20app%3F%26nbsp%3B%20It%20seems%20like%20the%20majority%20of%20comments%20today%20are%20around%20CPU%20usage%2C%20memory%20usage%2C%20latency%20for%20chat%20history%2C%20etc%2C%20but%20nobody%20seems%20to%20be%20willing%20to%20offer%20a%20meaningful%20comment%20around%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20two%20years%2C%20all%20we've%20heard%20is%20that%20the%20group%20is%20looking%20into%20improving%20performance.%26nbsp%3B%20Does%20that%20mean%20a%20new%20app%20is%20coming%20out%20soon%20NOT%20built%20on%20the%20'super%20efficient'%20Electron%20rails%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-898206%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EPerformance%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-898537%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-898537%22%20slang%3D%22en-US%22%3EI%20guess%20we%20will%20have%20some%20updates%20around%20Ignite%2C%20but%20for%20now%20not%20specific%20news%20on%20Teams%20Client%20performance%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-901121%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-901121%22%20slang%3D%22en-US%22%3ETeams%20has%20been%20improving%20over%20time.%20If%20you%20compare%20Teams%20client%20today%2C%20vs.%20Teams%20client%20last%20year%2C%20there%20is%20a%20massive%20difference%20in%20performance.%20There%20def.%20is%20more%20work%20that%20could%20be%20done%2C%20but%20I%20have%20definitely%20noticed%20changes%20being%20introduced%20over%20time.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-901145%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-901145%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree%2C%20Teams%20is%20using%20less%20resources%20now%20than%20a%20year%20ago.%20But%20there%20is%20still%20room%20for%20improvements.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F28313%22%20target%3D%22_blank%22%3E%40Dustin%20Halvorson%3C%2FA%3E%26nbsp%3BI%20guess%20you%20have%20seen%20the%20uservoice%20about%20this%20and%20Microsoft%20answered%20there%20that%20they%20have%20improved%20performance%20for%20the%20Teams%20client%20and%20they%20are%20still%20working%20on%20improvements.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F17219609-teams-uses-600mb-and-is-super-slow%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F17219609-teams-uses-600mb-and-is-super-slow%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-901314%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-901314%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20though...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20897px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F136026i39C8903C13CE20ED%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22TeamsRAM.png%22%20title%3D%22TeamsRAM.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EThat's%20just%20the%20client%20sitting%20idly%20in%20the%20tray%2C%20within%20our%20company%20tenant%20with%20just%2010%20teams%20or%20so%20I've%20joined...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-902423%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-902423%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F28313%22%20target%3D%22_blank%22%3E%40Dustin%20Halvorson%3C%2FA%3E%26nbsp%3Bthere%20are%20no%20plans%20that%20I've%20heard%20of%20for%20any%20new%20app%20not%20built%20on%20Electron.%20There%20have%20been%20significant%20enhancements%20to%20Teams%20that%20make%20it%20faster%20for%20things%20like%20starting%20chats%2C%20navigating%20etc.%20There%20are%20still%20a%20few%20areas%20of%20this%20to%20come%20e.g.%20faster%20tenant%20switching.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFundamentally%20Teams%20client%20will%20continue%20to%20operate%20like%20a%20browser%2C%20with%20a%20memory%20footprint%20like%20a%20browser.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-902676%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-902676%22%20slang%3D%22en-US%22%3E%3CP%3ESure%2C%20try%20telling%20this%20to%20anyone%20running%20Teams%20on%20a%20laptop%2Fnetbook%20with%204GB%20RAM%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-903309%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-903309%22%20slang%3D%22en-US%22%3EI%20mean%20I%20guess%20technically%20in%20that%20case%20if%20you%20run%20out%20of%20memory%2C%20then%20Memory%20usage%20%3D%20performance%20lol%20%3A).%20I%20remember%20it%20used%20to%20use%20like%201.2GB%20or%20something%20crazy%2C%20I%20don't%20usually%20see%20it%20going%20much%20over%20750MB%20these%20days%2C%20it%20def.%20can%20still%20use%20some%20tweaking%20which%20I'm%20sure%20will%20continue%20to%20improve%20over%20time.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-916308%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-916308%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3BYet%20the%20minimum%20requirements%20still%20say%202GB!%26nbsp%3B%20That's%20unrealistic.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20an%20organization%20that%20wants%20to%20move%20to%20Teams%20that%20has%20spinning%20disks%2C%20and%204GB%20of%20RAM%20in%20desktops%2C%20it's%20a%20product%20that%20is%20impossible%20to%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20frustrating%20to%20see%20the%20team%20continuing%20to%20post%20on%20things%20like%20integrations%20with%20third%20parties%2C%20when%20the%20core%20of%20the%20product%20is%20still%20extremely%20inefficient%2C%20and%20there%20doesn't%20look%20to%20be%20any%20priority%20put%20towards%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-916402%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-916402%22%20slang%3D%22en-US%22%3ETo%20be%20fair%2C%20I%20have%20never%20seen%20Teams%20Desktop%20client%20using%201%20GB%20neither%202%20GB%20ofr%20RAM%20memory%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-916442%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-916442%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20not%20just%20Teams%20running%20on%20that%20device%20though.%20And%20I've%20seen%20it%20very%20close%20to%201GB.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-916736%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-916736%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20there%20are%20no%20plans%20to%20move%20away%20from%20electron%20then%20the%20uservoice%20ticket%20should%20be%20closed%20as%20%22working%20as%20intended%22%20so%20people%20don't%20hold%20out%20hope%20for%20improvements.%26nbsp%3B%20If%20you%20aren't%20intending%20to%20fix%20performance%20then%20maybe%20focus%20on%20adding%2Fimproving%20teams%20functionality%20available%20via%20API%20so%203rd%20party%20clients%20can%20take%20over%20some%20of%20this%20performance%20work.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-902183%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-902183%22%20slang%3D%22en-US%22%3EMemory%20usage%20!%3D%20performance%20%3CBR%20%2F%3E%3B)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107251%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107251%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3BThanks.%20I%20agree%20memory%20is%20not%20exceeding%20~800mb%20lately.%20Maybe%20some%20update%20fixed%20this%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20the%20other%20hand%2C%20my%20CPU%20spikes%20were%20still%20dramatic.%20I%20fixed%20this%20by%20disabling%20the%20GPU%20rendering%20in%20Teams%20(strange%3F%20I%20would%20say%20GPU%20rendering%20should%20improve%20the%20performance%20instead%20of%20degrading).%3C%2FP%3E%3CP%3ESee%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.itexperience.net%2F2020%2F01%2F10%2Ffix-performance-issues-teams-high-cpu-memory-usage%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.itexperience.net%2F2020%2F01%2F10%2Ffix-performance-issues-teams-high-cpu-memory-usage%2F%3C%2FA%3E%3C%2FP%3E%3CP%3EHe%20also%20speaks%20about%20disabling%20the%20Outlook%20add-ins%20and%20integration%2C%20but%20actually%20I%20want%20to%20keep%20those%20features.%20I'm%20happy%20with%20the%20performance%20for%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107356%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107356%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F517831%22%20target%3D%22_blank%22%3E%40jimharpert%3C%2FA%3E%26nbsp%3Bwhy%20wouldn't%20you%20want%20it%20to%20use%20as%20much%20CPU%20as%20possible%20when%20it%20has%20something%20to%20do%3F%20Surely%20it%20should%20just%20do%20things%20as%20fast%20as%20possible%20and%20then%20be%20done.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1108157%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1108157%22%20slang%3D%22en-US%22%3EScrolling%20through%20the%20Teams%20chats%20was%20almost%20impossible.%20It%20took%2010%2B%20seconds%20to%20display%20the%20text.%20And%20when%20I%20scrolled%20up%2C%20it%20would%20take%20another%2010%20seconds%20to%20display%20the%20other%20posts%2Ftexts.%3CBR%20%2F%3ECPU%20was%20spiking%20at%20that%20same%20time.%3CBR%20%2F%3ENow%20I%20disabled%20that%20GPU%20rendering%2C%20and%20performance%20in%20teams%20has%20improved%20greatly.%20CPU%20is%20below%2010%25%20(which%20saves%20my%20laptop%20battery%20as%20well).%20SO%20I%20don't%20see%20any%20reason%20to%20enable%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1128273%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1128273%22%20slang%3D%22en-US%22%3ECan't%20believe%20how%20bad%20it%20is.%20I%20have%20a%20relatively%20new%206-core%20XPS%2C%20and%20Teams%20can%20bring%20it%20to%20a%20hault!%20Using%20up%2050%25%20of%20my%20CPU%20for%20absolutely%20no%20reason%2C%20and%20it%20just%20continues%20to%20run%20until%20I%20kill%20it.%20I%20had%20to%20switch%20to%20the%20web%20version%2C%20lol.%20How%20do%20you%20build%20a%20desktop%20version%20that%20performs%20worse%20than%20the%20web%20app%3F!%20Wow.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1109502%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Performance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1109502%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20randomly%2C%20daily%2C%20experiencing%20a%20laggy%20computer.%20Checking%20the%20Task%20manger%20when%20this%20happens%20reveals%20Teams%20using%2030-50%25%20cpu%20when%20I%20haven't%20touched%20teams.%20The%20cpu%20usage%20doesn't%20subside%20after%20a%20while%20either%2C%20it%20seems%20to%20keep%20doing%20it%20forever.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EForce%20closing%2Frestarting%20teams%20solves%20the%20issue%2C%20until%20tomorrow%20again%20I%20guess.%20Had%20this%20happen%20a%20few%20times%20last%20year%20as%20well%2C%20but%20it%20behaved%20well%20most%20of%20the%20time%20until%20recently%20where%20it%20happens%20more%20often.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Will anyone from the Teams product group offer an update on performance of the windows app?  It seems like the majority of comments today are around CPU usage, memory usage, latency for chat history, etc, but nobody seems to be willing to offer a meaningful comment around it.

 

For two years, all we've heard is that the group is looking into improving performance.  Does that mean a new app is coming out soon NOT built on the 'super efficient' Electron rails?

35 Replies
Highlighted
I guess we will have some updates around Ignite, but for now not specific news on Teams Client performance
Highlighted
Teams has been improving over time. If you compare Teams client today, vs. Teams client last year, there is a massive difference in performance. There def. is more work that could be done, but I have definitely noticed changes being introduced over time.
Highlighted

I agree, Teams is using less resources now than a year ago. But there is still room for improvements.

 

@Dustin Halvorson I guess you have seen the uservoice about this and Microsoft answered there that they have improved performance for the Teams client and they are still working on improvements.

https://microsoftteams.uservoice.com/forums/555103-public/suggestions/17219609-teams-uses-600mb-and-...

Highlighted

Is it though...

 

TeamsRAM.png

That's just the client sitting idly in the tray, within our company tenant with just 10 teams or so I've joined...

Highlighted
Memory usage != performance
;)
Highlighted

@Dustin Halvorson there are no plans that I've heard of for any new app not built on Electron. There have been significant enhancements to Teams that make it faster for things like starting chats, navigating etc. There are still a few areas of this to come e.g. faster tenant switching.

 

Fundamentally Teams client will continue to operate like a browser, with a memory footprint like a browser.

Highlighted

Sure, try telling this to anyone running Teams on a laptop/netbook with 4GB RAM :)

Highlighted
I mean I guess technically in that case if you run out of memory, then Memory usage = performance lol :). I remember it used to use like 1.2GB or something crazy, I don't usually see it going much over 750MB these days, it def. can still use some tweaking which I'm sure will continue to improve over time.
Highlighted

@Chris Webb Yet the minimum requirements still say 2GB!  That's unrealistic.

 

In an organization that wants to move to Teams that has spinning disks, and 4GB of RAM in desktops, it's a product that is impossible to support.

 

It's frustrating to see the team continuing to post on things like integrations with third parties, when the core of the product is still extremely inefficient, and there doesn't look to be any priority put towards it.

Highlighted
To be fair, I have never seen Teams Desktop client using 1 GB neither 2 GB ofr RAM memory
Highlighted

It's not just Teams running on that device though. And I've seen it very close to 1GB.

Highlighted

If there are no plans to move away from electron then the uservoice ticket should be closed as "working as intended" so people don't hold out hope for improvements.  If you aren't intending to fix performance then maybe focus on adding/improving teams functionality available via API so 3rd party clients can take over some of this performance work.  

Highlighted

@Chris Webb Thanks. I agree memory is not exceeding ~800mb lately. Maybe some update fixed this :)

 

On the other hand, my CPU spikes were still dramatic. I fixed this by disabling the GPU rendering in Teams (strange? I would say GPU rendering should improve the performance instead of degrading).

See https://www.itexperience.net/2020/01/10/fix-performance-issues-teams-high-cpu-memory-usage/

He also speaks about disabling the Outlook add-ins and integration, but actually I want to keep those features. I'm happy with the performance for now.

Highlighted

@jimharpert why wouldn't you want it to use as much CPU as possible when it has something to do? Surely it should just do things as fast as possible and then be done.

Highlighted
Scrolling through the Teams chats was almost impossible. It took 10+ seconds to display the text. And when I scrolled up, it would take another 10 seconds to display the other posts/texts.
CPU was spiking at that same time.
Now I disabled that GPU rendering, and performance in teams has improved greatly. CPU is below 10% (which saves my laptop battery as well). SO I don't see any reason to enable it.
Highlighted

I'm randomly, daily, experiencing a laggy computer. Checking the Task manger when this happens reveals Teams using 30-50% cpu when I haven't touched teams. The cpu usage doesn't subside after a while either, it seems to keep doing it forever.

 

Force closing/restarting teams solves the issue, until tomorrow again I guess. Had this happen a few times last year as well, but it behaved well most of the time until recently where it happens more often.

Highlighted
Can't believe how bad it is. I have a relatively new 6-core XPS, and Teams can bring it to a hault! Using up 50% of my CPU for absolutely no reason, and it just continues to run until I kill it. I had to switch to the web version, lol. How do you build a desktop version that performs worse than the web app?! Wow.
Highlighted

Hello I am still seeing 60% CPU usage and 40% memory running the Teams app in background. I noticed my laptop fan working overtime and running super hot, and it is all Teams doing this without even being in the foreground. If this is 'significant improvement' as everyone has said they have made, the bar must be very low.

Highlighted

@Chris Webb it still regularly uses 1.5GB RAM and over 30% CPU during meetings, slowing our 8th Gen Intel i5 CPU 8GB RAM HP EliteDesk G4 Mini PCs to a crawl when users have so much as 5 Chrome tabs, the Outlook 365 Desktop app, the OneNote UWP App, and the Microsoft To-Do app open.

 

Normally I would agree that memory usage != performance issues, however, when your machines have to split available RAM between the integrated graphics and other mandatory company programs, it's hardly acceptable to see Teams using 20% of the total available, especially when other apps built on the same ElectronJS platform (Discord & Slack, for example) manage to consume almost nothing during a call or when switching text channels.

pastedImage_30.png

 

When I use MS Teams to join meetings from my home computer with a 4th Gen i7 and 24GB RAM, it still chugs while utilizing the same resources, albeit a tad less CPU. To be clear, my home PC is able to switch to other applications a little faster, but the extra RAM and processing power don't seem to help Teams performance at all, indicating a problem with the code that makes up Teams' core.

 


I understand development takes time, but it's going on 3+ years now with Teams still exhibiting performance issues. Maybe it's time for a rewrite of Teams from the ground up similarly to Slack's recent rewrite?

 

Tagging @Juan Carlos González Martín and @jimharpert so they can see Teams using more than 1GB RAM at least once in their life. Also looping in @Vasil Michev and @Eric DeVaudreuil because they're spot on with their prior comments about high resource usage. Also making @Steven Collier aware of why one might not want to see a single application utilize such high amounts of resources.

Highlighted

It's a lost cause mate, that's how "modern" development works.

Highlighted

@Vasil Michev Agreed. Companies these days go "Are people paying for it? yes? then it's not worth spending time fixing"

 

People need to start talking with their wallets. When the money stop flowing they start listening.

Highlighted
Spot on. I provide IT Consulting services for but a small number of clients, but of my clients the 50-60 currently using Office 365 E3 are very close to ditching Microsoft for email from Google Suite and chat from Slack. Quite sad it has to come to this point just to help companies understand what makes or breaks their products.
Highlighted
Bumb
Highlighted

Not even running a call, video, or meeting, just normal chat. 1.146GB of memory, lots of CPU as well. Version: 1.3.00.4461 (64-bit). It was last updated on 3/3/20.

Highlighted

@Dustin Halvorson,

Thank you for rising this issue. 

I gave Teams a chance starting to work with it a few weeks ago and ever since I am wondering what the heck is going on with my laptop performance. Now I realized it all came from Teams.

Not to mention the absolute non-intuitive interface, permanent lag and so on. 

Good bye Teams! See you next year, maybe somebody near Satya will redesign it. Or get another app instead. 

Highlighted

Also surprised this isn't mentioned more. I guess just most people aren't using Teams. Regularly causing issues this way too. 30% CPU and 1.5GB RAM used (commonly makes Outlook also use 30% CPU too) 

 

4 way video meetings expect 100% CPU and 2GB RAM. Running on:

Intel Core i5-8365U

8GB DDR4 RAM

 

Plenty businesses still on 4GB RAM so ... :sad:

Highlighted

@Learnasyougo one of my IT clients is looking to switch their entire office from a mix-mash of subscription services over to an all-in-one Office / File Collaboration suite, so this is just another consideration I have to take into account despite them running 4th gen i5 Dell business all-in-ones with 8GB RAM and a barebones Windows installation.

 

The heavy resource usage by the Outlook desktop application will definitely be a deciding factor as we evaluate spending $12 CAD per seat on licensing. (In case anyone at Microsoft is motivated by more revenue, that'll be around $1000 CAD per year for this particular office - not a lot compared to large organizations, but still a chunk of money none-the-less.)

Highlighted
We use Teams and Outlook latest versions on 8GB ram machines with no issues. There must be something there causing the issues somewhere in the chain.
Highlighted

On my clients machines we run nothing other than a fresh install of Windows 10 Pro (installed directly from Microsoft's own Media Creation Tool), Google Chrome, Office 365 Business, and Windows Defender. On my day-job's work PC's we run the same specs, although have newer 8th gen i5 processors, and Teams still chugs along sluggishly when in meetings or switching between channels.

 

Don't get me wrong; I'm enjoying the integration with Office 365 apps that Teams brings to my workday, as it allows for improved collaboration, however...


"if I'm constantly battling the sluggishness of Teams' user interface, am I really more efficient than if I were simply not using Teams?"


Discord, Slack, WebEx, Zoom, GoTo Assist, TeamViewer, or even Microsoft's own Skype all utilize less than 5-10% CPU and never go above 300-500MB memory at most during meetings, so that kind of narrows things down to the problem being Teams itself.

 

As I said before: maybe it's time to rewrite Teams from scratch like Slack did last summer, or at the very least, conduct an in-depth user-study to understand why it eats resources on certain systems.

Highlighted

Well, many of us still struggling with this. @Chris Webb  Following my experience during Teams implementation on Citrix (with resource offloading) Teams reducing 30-40% of the server density, comparing with Skype For Business. I have also learned, that Teams using a lot of cache file mechanisms in order to reduce ram footprint, so does not really help for SSD wearing, and just simply kills an HDD based machine. But still knowing the development challenges that confirmed on various channels, the app is still sluggish in 2020/05, (and was the same problem in 2018, when we started to use Teams... )

I do not think corporate Office or blue-collar users must use at least 8th+ generation Corei5 machines and AMD Ryzen 5 (Zen+) or better CPUs, in order to use the solution quite smoothly.  If I use my workstation (HP Zbook G6 with 6cores, 12threads), I feel a significant performance drop, when we turn on a camera or use only for audio meetings.  A HyperV machine not doing that drop! I can also admit, that was some improvement from 2018, but just some. I personally think: Instead of focusing on funny features, like shiny background on-camera meetings, will be better to optimize the app core I think. 

Highlighted

@Sirus86

 

we are having the same issues, but running a mix of different surface pro's included the latest 7th gen.

 

The irony is, we are due to be pitching to Microsoft corporate for some consultancy work next week using Teams, and we know the presentation will be awful because of their own software/hardware issues.

Highlighted

I just wanted to add another voice to this thread. As with many IT shops, we're understaffed, and recurring problems significantly reduce our productivity. When answering help desk tickets for a few hours a day, there are always requests for help with Teams being sluggish. Just about every "performance" issue I've dealt with over the past year has been related to Teams usage. Specifically, when I ask the user to exit Teams, everything works well. When they relaunch Teams, things run well for a bit and within minutes the problems return.

 

What should be interesting for any Microsoft employees listening here is that we've been exclusively using Surface Book 2 machines for the past 2 years. Ours are 8th-gen i7s (4C/8T) with 16GB of RAM and 512GB eSSDs. That should be plenty of processing power to run just about any office productivity application. Teams causes us problems.

 

I anxiously await recommendations and solutions from MS.

Highlighted

@pstone7 Just to mention we are noticing this problem too, sometimes Teams can take up 1GB+ of memory, and our whole system slows down.

Highlighted

@dhymeri Teams makes my Surface Pro 4 Core i7 16GB device almost unusable sometimes.

The fan goes like crazy all the time and typing in any program can be delayed and things stop responding and the Surface is red hot. It is always much worse when in a call too. Trying to access files on Teams whilst in the call barely works it takes that long.

 

They really need to re-develop in a more performant framework that doesn't need to run its own webserver.

Highlighted

Hi,

I'm running Microsoft Teams Version 1.3.00.13565 (64-bit) in my laptop with i5-63000U processor and getting high CPU usage below. 

 

jmoreno88_0-1593742719004.png