Blog Post

Microsoft Teams Blog
3 MIN READ

Microsoft Teams performance improvements reduce power consumption in meetings by up to 50%

robertaichner's avatar
robertaichner
Icon for Microsoft rankMicrosoft
Feb 09, 2022

In a previous post, we shared how Microsoft ensures efficient use of device resources such as CPU and memory during Microsoft Teams calls and meetings. In this article, we want to dive deeper into how our goals and measurement methodology has been used to cut power consumption in Teams meetings.


Why is this important? In addition to reduced energy costs, these optimizations lower the burden on an organization’s hardware and improve the consistency and efficiency of Teams meetings and calling experiences across devices.


One of the challenges brought on by the ubiquity of Teams is the need to create equitable experiences across an incredibly diverse Windows device ecosystem. We’re committed to ensuring great calling and meeting experiences for users on low-end hardware as well as those on high-end workstations and high-resolution monitors. One of the factors we’ve addressed is the difference in power requirements for different customer profiles by ensuring Teams meetings are as energy-efficient as possible, regardless of setup.


First, we created a test framework to accurately measure power consumption for important meeting scenarios such as group video calls and screen sharing, which often involve energy-intensive processes such as content capture, encoding, and rendering. The next step was to evaluate these processes and identify opportunities to optimize the efficiency of each. Isolating and optimizing each of these processes enabled us to reduce power consumption up to 50% for energy-intensive scenarios such as having over 10 users in a meeting when everyone has their video turned on (see figure below).

 

During our evaluation of the video capture process, we focused on camera optimization to reduce demands on the CPU when using video in meetings, improving configurations, reducing code complexity for auto-exposure, auto-white balance, auto-aliasing, resulting in power draw reduction from the onboard camera and stability enhancements, and face detection processes. Then, we turned to video rendering, particularly for meetings with many participants, where the users receive a video stream for each participant displayed in the Teams client. Incoming videos can have different resolutions that require the client to rescale each. A simple 3x3 video grid once required nine distinct rendering operations. By combining the streams and composing them into a single video, we have been able to consolidate operations in video rendering and significantly reduce the power requirements for each device used.


A couple of the optimizations we released in 2021 focused on using the native resources of operating systems to improve how image fragments are transferred during the rendering process, as well as allowing Teams to tap the device’s graphic processing unit (GPU) dedicated to support improve rendering performance. This approach has also been extended to the user's video preview. Looking forward, we’ll continue to work closely with CPU and GPU chipset vendors to ensure the next generation of silicon is further optimized for Teams video conferencing.


Recently, we released rendering optimizations targeting individual screen components that have led to additional reductions in power consumption for video and application sharing. More screen-sharing optimizations are planned for later this year.


Similar to our other performance improvement initiatives, these power consumption improvements are subjected to progressive testing to validate the intended benefits across customers and environments. Additionally, we evaluate each new planned Teams feature to ensure existing processing efficiencies are not compromised.


So while we continue to launch innovative Teams features to help people connect and collaborate in new ways, we’re also dedicated to making sure these experiences are optimized for all users, regardless of their network and devices.


Continue to watch this blog to learn about new Teams features and optimizations designed to improve the quality of your calls and meetings.

Updated Aug 25, 2022
Version 5.0

18 Comments

  • macardwell's avatar
    macardwell
    Copper Contributor

    It is great to see that you are working on performance improvements.  1.5.00.2164 seems to show clear improvements in both memory and CPU usage.  I still don't understand why you are using Electron 10.47 and Chromium 85 when the current stable releases are Electron 17 and Chromium 98 which would take advantage of the performance improvements in those projects. 

     

     

     

     

     

     

  • cpressland's avatar
    cpressland
    Copper Contributor

    Using Microsoft Teams on my MacBook Pro M1 Pro takes my battery life from around 18 hours to 8 hours. When I'm working remotely I usually exclusively use the iOS App unless I really need to open Teams on my Mac. It's good to see that power efficiency in Teams is improving and is a priority for Microsoft, but it's just not improving enough. No other application, even running full development stacks with Postgres, Redis, Python, Golang, and VSCode make a dent on my battery life and performance quite like simply launching teams does.

  • I'm not sure... are these improvements already released? Because we don't see any improvements since January 2021... RDS Server are eating memory and CPU even when there is no big workload in Teams. One thing might be the integrated Office Web but it still eats just too much memory and cpu.

    Teams 2.0 for Business still isn't released, while on Windows 11, we see articles claiming to save up resources if you turn off the Teams + Widget https://windowsreport.com/save-system-resources-by-disabling-unused-widgets-in-windows-11/, which concerns us (Teams Home for Windows 11 - which by the way still doesn't support interoperability with Teams for Business / Teams Work - is based on the new shiny webview2 runtime instead of electron) and doesn't foreshadowing the appraised performance improvements.

    But to be fair, we always recommend to do meetings on a fatclient instead of doing so on RDS Server. So while we don't see any improvements in overall usage of MS Teams, meetings might have improved.

    Thank you for your continued work on Teams! There are still many features of the product, that need further improvements.

  • Nathan_FBR's avatar
    Nathan_FBR
    Brass Contributor

    Look forward to improvements! Our whole fleet of Latitudes heat up like crazy when Teams meetings are running. Heat and the fans running at 100% are our biggest complaint from users.

     

     

  • bala91's avatar
    bala91
    Copper Contributor

    Good to know the power consumption has been reduced by 50%. The meeting participants from low speed internet connectivity locations struggle to join Teams meetings. In view of this many invitees prefer other options like Zoom or Google Meet. Is there any plan to address this

  • What about native macOS version for M1? What is the roadmap for this ? Team is falling hugely behind as all of the other systems (Zoom, Webex, Slack) are running native.

  • ediflyer's avatar
    ediflyer
    Brass Contributor

    I must say I'm incredibly surprised to read of all these power saving improvements that are apparently already in place. On my Core i7 Dell XPS 13 the battery life totally tanks if I'm in a Teams video call, with high CPU usage and a very warm laptop. I've tried hardware acceleration on and off. Certainly no signs of any improvement compared to a year ago that I've seen!