My feedback

  1. 2,044 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    229 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    One more note, that article on how Teams uses memory (as much as it wants) - is crazy! Try running Teams on a 30 user RDS host, it is a business class app correct. I understand Electron is easy to dev for and cross platform friendly, but if it’s this bad on resources it makes Microsoft as a whole look, quite frankly - lazy. We are a MSP, and we need to explain all the time that Microsoft simply doesn’t care or it would be fixed (over four years)!

    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    I concur, there was no reason to split this issue - it all boils down to performance and resource usage. It might not crash if it wasn’t trying to use 1.5 GB of RAM.

    I guess an issue with 18k votes was getting to be an issue. I use Teams on a 12 Core 32Gb RAM, NVMe storage workstation and IT.IS.STILL.SLOW. Just try searching a chat thread and see what happens.... ludicrous this hasn’t been resolved in 4 years, likely because it would have to be re-written natively vs using Electron. We have to discourage our customers using it, even if they already have a license under 365.

Feedback and Knowledge Base