Andres S

My feedback

  1. 7,032 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.

    ~Alex

    Andres S commented  · 

    Las time @Warren responded was September 9, 2018. That is like 8 months ago. He said several weeks... so what happened?

    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.

  2. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Public » Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S supported this idea  · 
  3. 30 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S supported this idea  · 
  4. 72 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S supported this idea  · 
  5. 11 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S supported this idea  · 
  6. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S supported this idea  · 
  7. 40 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S supported this idea  · 
    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.

  8. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    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.

  9. 2,677 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    254 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Suphatra responded

    So happy to share that this is off the backlog and we are actively working on it!

    -Suphatra

    Andres S commented  · 

    +1 😬

Feedback and Knowledge Base



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.