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
Another teams blog with a hard sell on features for the us government and entry level / free licenses. Another blog that doesn’t mention OS X
I may as well just sign zoom contract and commit my future to google workplace. This program is never getting fixed, clearly. All the added security of Microsoft goes out the window when you can’t open teams. I am truly perplexed that this is such a non priority. All I can think is that they somehow see teams as pivotal to avoiding windows defection. I can’t think of any other reason this product is still unusable.
I may as well just sign zoom contract and commit my future to google workplace. This program is never getting fixed, clearly. All the added security of Microsoft goes out the window when you can’t open teams. I am truly perplexed that this is such a non priority. All I can think is that they somehow see teams as pivotal to avoiding windows defection. I can’t think of any other reason this product is still unusable.
- Not sure if anyone mentioned this on the 11 pages here but this also affects the Windows client. I've had to restrict users from running Teams on remote desktop servers because of the huge amount of I/O it generates upon startup which slows down everyone else, not to mention the amount of disk it uses. Electron apps are bad enough with the CPU and memory they take up, but when you start pounding the disk mercilessly like this it kills your performance for any other users sharing the machine too!
- It's quite common for larger organisations running Teams through their enterprise infrastructure to request users to turn video off as the load is too great. So it becomes a conference call platform with presentations.
- Oh yes we definitely tell users that if you're using Teams on remote desktop, it's just for chatting really. But even that takes up a LOT of I/O when starting up, it's crazy. Even opening it up in Chrome seems to use so many Service Worker threads, I think they need to put a damper on that.
