Forum Discussion
Solved
Teams is KILLING my Mac Every Day
I have a hard time believing I'm the first person to post this after not finding anything in the forum. I wouldn't doubt if Microsoft is deleting them because they can't figure out how to fix this i...
Hi everyone, we're pleased to announce Microsoft Teams for Apple Silicon, which on the M1/M2 ARM builds, will have significantly faster performance than what's seen during the Rosetta emulation today! Here's our official roadmap ID for this release; Microsoft 365 Roadmap | Microsoft 365. More on this can be found here; Announcing Microsoft Teams optimized for Apple silicon - Microsoft Tech Community.
Users should see a significant performance boost with this release. And for the Intel Macs out there, we're still thinking about you! We have some large performance fixes coming that will help improve overall performance for the Intel version as well.
Thanks,
Sam Cosby, Teams Engineering PM
Using 1.4GHz Dual Core i5, iMac 21.5-Inch from Mid 2014. It is exceedingly unoptimized for MacOS and for my iMac to be able to function with teams in a way that is productive at all is impossible. It causes aggravation while I have a secondary monitor plugged in and it is absolutely killing my machine's productivity even when minimized. It is affecting co-worker image of Apple hardware despite the issue being a slow intel 1.4 processor with a very Chatty app on the Microsoft end, Please don't let people end up getting frustrated.. With ignorance around MacOS use in general things tend to get ugly pretty fast in the workplace. for years things like this have plagued cross platform software with the blame being cast across both Aisles.
Opening FS Usage, reveals when Teams is opened, Application "Microsoft Teams" HAMMERS my SSD, and File System with an obnoxious level of I/O requests, the saturation caused by excessive reads, and writes is just as saturating the the internal Bus as having a key being held down throughout your entire workflow somewhere on the keyboard... THIS IS LOOKING SIMILAR TO EARLY ADOBE CC ISSUES THAT CAUSED CRASHES, and EVEN GPU DAMAGE THAT EXACERBATED THERMAL ASPERITIES IN DRIVES AND DISRUPTED BGA VOIDS PRESENT IN GPUs. You guys have successfully built a bomb into your program for the MacOS Users to be angry about.
Please note: it's absolutely obvious to everyone that it is the 'Teams Client. Despite some systems poor attributes. I just Instammed an M2 Drive and if that is causing me trouble with one of those installed, then anyone with a mechanical drive is really dead in the water until Vast Optimizations are routed.
Devs be wary, this is a major issue because of the contention between apple and Microsoft over SW. Final Cut may or may not run smoothly on other systems but both companies have a duty to help each other look good when using respective software cross platform... As end users we are very fickle, we cant be just left to attribute this issue to platform hardware or have others outside the engineering departments put in their two sense.. This may divide Cross-platform OS end users due to lack of interest and cause a PR issue for Microsoft. But the diehards are just waiting for Microsoft to get along with Apple (Vice Versa)
Opening FS Usage, reveals when Teams is opened, Application "Microsoft Teams" HAMMERS my SSD, and File System with an obnoxious level of I/O requests, the saturation caused by excessive reads, and writes is just as saturating the the internal Bus as having a key being held down throughout your entire workflow somewhere on the keyboard... THIS IS LOOKING SIMILAR TO EARLY ADOBE CC ISSUES THAT CAUSED CRASHES, and EVEN GPU DAMAGE THAT EXACERBATED THERMAL ASPERITIES IN DRIVES AND DISRUPTED BGA VOIDS PRESENT IN GPUs. You guys have successfully built a bomb into your program for the MacOS Users to be angry about.
Please note: it's absolutely obvious to everyone that it is the 'Teams Client. Despite some systems poor attributes. I just Instammed an M2 Drive and if that is causing me trouble with one of those installed, then anyone with a mechanical drive is really dead in the water until Vast Optimizations are routed.
Devs be wary, this is a major issue because of the contention between apple and Microsoft over SW. Final Cut may or may not run smoothly on other systems but both companies have a duty to help each other look good when using respective software cross platform... As end users we are very fickle, we cant be just left to attribute this issue to platform hardware or have others outside the engineering departments put in their two sense.. This may divide Cross-platform OS end users due to lack of interest and cause a PR issue for Microsoft. But the diehards are just waiting for Microsoft to get along with Apple (Vice Versa)