Performance enhancements to Microsoft Teams lead to faster response times
Published Jun 02 2022 08:00 AM 38.6K Views
Microsoft

Over the past year we’ve delivered enhancements to Teams that improve its overall interaction responsiveness time and creates a more fluid experience for the user. Investments have included transitioning from Angular framework to React, upgrading Electron (a framework for building desktop applications), reducing re-rendering, and making incremental improvements to the code. Our desktop, framework, and performance teams made several foundational improvements and our messaging and calling/meeting teams partnered to optimize the code for targeted user experiences we identified as important to the overall experience.


To gauge our progress, we recently looked at anonymized data from the 95th percentile of all desktop users in the world (meaning that 95 percent of the time the experience is better than this metric). We tend to focus on the 95th percentile because it includes users on low end devices, users on low bandwidth networks, and incorporate other edge cases that can impact the user experience.

 

The data showed notable improvements in messaging and meeting experiences as seen today vs. August 2021.

 

Improvements in latency and page load times for messaging

When users scroll over the chat list, latency has improved by 11.4%, and scrolling over the channel list has improved by 12.1%.


The compose message box loads 63% faster, enabling the user to type a message immediately once they switch into a chat or channel.


Page load times are much shorter as well:

  • The time to switch to a channel and to open a chat window-both were dramatically improved by 25%
  • Switching threads in the activity feed has improved by 17.4%
  • Switching between chat threads has improved by 3.1%


Greater fluidity and reduced lag in meetings

The mute and unmute audio response during a call improved by 16%.


Navigating to the ‘Pre-meeting join’ screen is 9% faster.


Opening a calling/meeting window loaded 4.5% faster. Then once a user is in a meeting switching into a chat improved by 13%, switching to the activity feed improved by 18.7%, and switching to a channel improved by 20%.

 

Infographic.png

 

These improvements complement the power reduction improvements shared in the recent blog "Microsoft Teams performance improvements reduce power consumption in meetings by up to 50%."


We continue to focus and invest in Microsoft Teams performance optimization and value the customer and partner feedback that helps us to prioritize the most critical scenarios.

16 Comments
Brass Contributor

Hi @Mark_Longton,

thx for the effort, spirit, and work that you and your colleagues are bringing into the Teams development process. This is greatly appreciated from the community :stareyes:

 

Are there any life signs of the new WebView2 based Microsoft Teams Client for Business Users? We're hoping that with this new client the responsiveness, performance and UX is, what we're praying for :hearteyes:

 

A TeamsFanBoy from Germany

@Philipp_Kohn 

Microsoft

@Philipp_Kohn Thank you for the comment.  I can say that there is a heavy resource allocation towards the WebView2 work you mention for business users @Philipp_Kohn although I am not able to comment on any timeline at this time.   Fully appreciate the need to keep pushing hard in this area across responsiveness, latency, and resource utilization both with short team gains and longer term architectural changes to achieve step function improvements.  Thanks again.

Brass Contributor

Is this based on windows devices, web, mobile or Mac? 

crossing them seems a bit disingenuous in some cases, many mac users would love to see this breakdown on Mac, which would not appear to share these improvements anecdotally. 

Brass Contributor

Interesting to read, however which version of the app does this blog refer to? I just got a new laptop with Windows 11 but when I went to sign into Teams (having been impressed at first to see it built in to the OS), I was told this wouldn't work for my organisation account and I would have to download Teams for Work/Organisations. I duly did so, but it didn't seem that power efficient or snappy so I'm wondering if it's an older version that doesn't have the changes you're discussing here. Do you know when these different versions are going to be merged? It's all a bit confusing. 

Iron Contributor

You will never improve performance enough to make everyone happy since you are using web technology instead of native. Also with such a big audience it will be very difficultly to make everyone happy overall with the client.

 

Would be cool if you ever decided to support an open protocol like https://matrix.org/ then there could be many more clients for many platforms at no extra cost to you (besides adding support). While at the same time giving everyone the possibility to find the client that suits them the most (or even building their own). Matrix also adds the possibility of more collaboration with external users that do not use Teams.

Microsoft

The metrics shared are based on the 95th percentile metrics on desktop devices.  Many of the approvements made will apply to web as well.  

 

This specific blog is referring to the business version of Microsoft Teams.  The version integrated in Windows 11 is what you can use with your MSA account.  We have more improvements coming for the business version including larger architecture improvements although I am not able to share the timeline at this time.  

Brass Contributor

Many thanks for the reply @Mark_Longton. I'm not sure what an MSA account is - I tried signing in to the version built in to Windows 11 with my work one (NHS Scotland, I believe E5 licence if that helps?) and it said I couldn't use my work one with it and had to download a different version. As I say if the desktop versions could be merged that would be much less confusing from an end-user perspective and I find performance is fine as-is, my key request would be for far lower battery usage, esp when in a call. Thanks :) 

Copper Contributor

@ediflyer Your MSA account is one that ends in @hotmail.com or @outlook.com for example.  This would be a personal account.  The App built into Windows 11 ONLY supports these MSA accounts today.  If you want to use the Work & School Accounts (associated with your business/school) then you would want to download the Teams App directly.  There is a Microsoft Store version as well.

 

The one built into Windows 11 is based on WebView2 and the Work/School one is based on Electron.  Eventually the Work/School will be transitioned to WebView2 and then you will see even more improvements.

 

Richard

Brass Contributor

@rbrynteson that's really helpful and makes sense, thanks. I never use the personal version, only the work one so I can't wait to see more improvements in efficiency. I find when I'm in a call my GPU usage is at about 20% (CPU 9% or so, Core i7) and it really hits the battery - about 100% to 80% after a one hour call (albeit with screen brightness up a fair whack too), anything to cut that back would be amazing (and mean the fans didn't kick in as much too!). 

Brass Contributor

You know what it would actually make it fast and enjoyable?

 

Drop Electron and use native languages, like Skype used to before Microsoft's acquisition.

Copper Contributor

Hi @Mark_Longton , the pictogram shows "Open call/meeting +63%", but the sentence says "Opening a calling/meeting window loaded 4.5% faster". Which is correct?

 

Microsoft

@Shinnosuke_Takeda  the text is correct. Thank you for calling this out.   I have a request to get this updated.

Brass Contributor

Does anyone know from which version of Teams these improvements will be noticeable? 

Copper Contributor

Still runs like **bleep**.

Copper Contributor

Moving from skype, the performance has degraded noticeably. Taking seconds to load in a channel fully and overall sluggish UI.

 

A simple thing such as sending a text to a bulletin-board should be quick and responsive. Everything else is second to this, yet it has become an overall "meh" experience. If this app is to compete in any shape or form with something alike to Slack, the performance *needs* to go from seconds to sub-second loadtimes on medium-end hardware.

 

Oh and btw, these improvements are a great step in the right direction, but percentage improvements tell me nothing. 11% can be anything from years to milliseconds, and as hardware always differ from oneanother, example timings and hardware is much more intuitive.

Copper Contributor

Hi @Mark_Longton 

Thank you for sharing these performances enhancements. I would be able to measure and demonstrate them to my end users but I have no tools for that.

Could we have nominal average delays to expect on a few test protocols including Teams version, OS version, hardware and network connection in place of percentage ? This way, we'll be able to compare ourselves and to argue for an investigation on our company context.

And we really need timeline visibility about the next release bringing performance improvements.

 

Version history
Last update:
‎Jun 06 2022 08:05 PM
Updated by: