Andres S

My feedback

  1. 2,442 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

    259 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your continued feedback. We are continuously improving the clients to use less memory and RAM.

    The upgrade to Electron 10 has rolled out fully to the public at this point. Telemetry and testing has shown that this is helping to improve memory performance on the client.

    We will continue to work on improvements, and will share more updates as they become available.

    For more details on how Teams currently uses memory, please visit https://docs.microsoft.com/en-us/microsoftteams/teams-memory-usage-perf.

    Andres S supported this idea  · 
  2. 1,275 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

    working on it  ·  94 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S supported this idea  · 
    An error occurred while saving the comment
    Andres S commented  · 

    Hi, well, same here. I started noticing my laptop going full wind blast mode for no reason and traced it to Teams using 100% (of one CPU thread).

    In my laptop's case, that is 12.5% (100% CPU / 4 cores / 2 threads per core = 1 thread running at 100%).

    Going over its execution details on Process Explorer, found that there is one thread which starts at "IsSandboxedProcess+somenumber" and that thread is stuck on "waiting thread sync". That thread had used *a lot* of CPU Process Explorer claims.

    So, this process is stuck on a deadlock situation of sorts, my very rusty developer gut tells me. If that is the case, thats a crass bug.

    Once quit Teams (using its own Quit command), the wind turbine mode on my laptop stopped, almost immediately.

    Once I started Teams, it didn't go CPU crazy. My laptop had just resumed from sleep.

    I have no more time to delve deeper into this, hopefully this information helps - somehow. Teams is quite slow, but now being CPU hog... not good.

    I will cross post this on other threads I find relevants, apologies in advance.

    --------------
    leafblower....lol good description.

  3. 3 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

    1 comment  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andres S commented  · 

    Hi, well, same here. I started noticing my laptop going full wind blast mode for no reason and traced it to Teams using 100% (of one CPU thread).

    In my laptop's case, that is 12.5% (100% CPU / 4 cores / 2 threads per core = 1 thread running at 100%).

    Going over its execution details on Process Explorer, found that there is one thread which starts at "IsSandboxedProcess+somenumber" and that thread is stuck on "waiting thread sync". That thread had used *a lot* of CPU Process Explorer claims.

    So, this process is stuck on a deadlock situation of sorts, my very rusty developer gut tells me. If that is the case, thats a crass bug.

    Once quit Teams (using its own Quit command), the wind turbine mode on my laptop stopped, almost immediately.

    Once I started Teams, it didn't go CPU crazy. My laptop had just resumed from sleep.

    I have no more time to delve deeper into this, hopefully this information helps - somehow. Teams is quite slow, but now being CPU hog... not good.

    I will cross post this on other threads I find relevant, apologies in advance.

Feedback and Knowledge Base