garygraeff Sorry to hear you're having this problem. Let's dig into this a bit further.. I read the previous post as well and it looks like this seems to be happening after the initial login process.. Can you provide detailed steps that you can help pinpoint about the specific timeframe for when you see this? An example would look like;
- At 4:42:00, I launched SpeedTest, showing X upload/download speeds, then launched Teams.
- At 4:42:10, Teams fully launched, still showing X upload/download speeds.
- At 4:43:05, SpeedTest is now showing Y upload/download speeds.
- At 4:45:06, SpeedTest is still showing Y upload/download speeds.
- At 4:45:00, I killed the Teams.exe Process, and SpeedTest went back to showing X upload/download speeds.
When clearing cache (Sign-out also clears cache), there's a rebuilding process that takes place for the app to try and rebuild that cache so you have a better experience when in the app. That's expected to take some network speeds with it as it's downloading history/etc. Even when the app is idle, we're still making continuous calls to the service to ensure you're continuing to have things up-to-date (presence, chat feeds, notifications, etc), that can also continue to require bw speeds. But in your case, looking to understand the specific repro steps that cause this in your case to see if there's indeed a real problem here from the Teams side, or if there's a network processing issue locally via the OS.
Thanks,
Sam Cosby, Teams Engineering PM
