I've been dealing with frustrating performance problems in Microsoft Teams over the past three years across two laptops. It seems like Windows is prioritizing the wrong CPU cores while I'm on a Teams call, especially if the app isn't the active window. After moving to a new Intel 125H laptop with an updated CPU architecture, my experience has improved. I'm curious if anyone else has faced similar issues or if my theory about core scheduling, particularly related to Intel's P/E core system, makes sense. Here's what I've observed: when I monitor the CPU usage in Task Manager, it shows that while Teams is the active window, the performance is normal, but switching focus to another window causes the performance to drop significantly, with E cores spiking to 100%. I've tried various solutions, from cleaning my laptops to checking network stability, but the problem persisted until my recent hardware upgrade. Is there a known root cause or fix for this issue?
5 Answers
It’s likely that your older laptops were set up with power plans that didn’t optimize core performance effectively. The newer laptop might be better configured out of the box for multitasking and video calls. Also, many Teams issues stem from its architecture; being built on technology similar to Chrome can lead to inefficiencies during heavy use.
This is an intriguing issue! Core scheduling should be moving less critical tasks to the E-cores while keeping demanding applications like Teams on the P-cores. The Intel Thread Director plays a crucial role in managing this, but if it doesn’t function as intended, you might see performance drops like you've described. Considering that Windows 11 has improved handling for these cores, it might be worth checking out any updates or tweaks for the Thread Director. Have you looked into that?
Your findings might indicate that newer hardware configurations better handle these scenarios. It might be worthwhile to look into whether other users have reported similar experiences with prior models, especially as more new Intel chips are deployed. Have you checked any online forums for more anecdotal evidence? There could be underlying tweaks that others have discovered!
Looks like a classic example of how that P/E core switch can affect software performance! You’re right to suspect that poor core scheduling could trigger these issues. It's not uncommon for the system to struggle when tasks aren't efficiently routed. It seems like you've done your homework on this, but I’d suggest looking into tasks and their priority as well; changing that could give you a boost!
Hey! It sounds like you’ve been through a lot with the Teams performance! What you're experiencing isn't necessarily a bug; Windows tends to shift background tasks to the E-cores to keep the system responsive. However, since Teams deals with multimedia, it should ideally get more resources on the P-cores. You might want to experiment with the multimedia scheduling settings to see if that has any effect on performance. It's a known issue that memory-heavy tasks can suffer on E-cores, so adjusting those settings could help!
That makes a lot of sense! Teams and Edge WebView 2 can be quite memory-hungry, so it’s likely that's causing the stall when backgrounded.
Exactly! Everything modern tends to rely heavily on resources like RAM, especially with Teams running in a WebView environment.