Chromium tunes Teams memory usage on an ongoing basis in order to optimize Teams performance without impacting anything else currently running.
When other apps or services require system memory, Chromium gives up memory to those processes.
Whether you're running the Teams desktop app or the Teams web app, Chromium detects how much system memory is available and utilizes enough of that memory to optimize the rendering experience. It is important to understand the expected behavior of Teams when it comes to system memory, and to know the symptoms of truly problematic system memory issues. The following image shows side-by-side memory usages of the Teams desktop app for Windows and the Teams Web app (in this example, running in Google Chrome). See Chromium Memory Usage and Key Concepts in Chrome Memory for more information. More information about Electron is available at their Web site. Both the web app and the desktop versions use memory in a similar way to how a browser would use it. Another advantage of this architecture is there's a similar memory usage profile between the Teams web app and the desktop version. This parity is possible because Electron and Chromium maintain a similar code base across all versions. Teams being designed on Electron allows for faster development, and it also maintains parity between Teams versions across different operating systems (Windows, Mac, and Linux). This is the same rendering engine behind many of today's most popular browsers, including Edge and Chrome.
To achieve this, the Teams desktop client was developed on Electron, which uses Chromium for rendering. Teams is designed to use modern web technology. This article describes how memory is used by Teams, and why the Teams desktop application (app) and the Teams web app do not prevent other apps and workloads on the same computer from having enough memory to run optimally. Some Microsoft Teams users have questions about how Teams uses memory.
0 kommentar(er)
