This may technically be a bug but I'll add this anyway as a blanket item. The performance of the desktop client is just abysmal in my experience.

Clicking around constantly freezes the UI, and typing is painfully slow.

Teams has a bunch of difference local caches and temp files that just continually grow forever in %appdata%\Microsoft\teams. It would be great to have a button that would wipe out all the local cache and temp files in this folder. Doing it manually has a very noticeable performance gain throughout teams.

As it stands, I'm going to write a powershell script to run on all the workstations I manage periodically to close teams and clean this up as a refresh of teams.

Fix unnecessary activation of discrete GPU on MacBook Pro again. Seems to be regression on version 1.2.00.13765

Very slow

My goodness, every time you start Teams it's as though it's the first time. Most or all history is gone until it pulls it down from the cloud again. If you want us to use it, make it start in less than 60 seconds.

It is is just too slow :/

Teams desktop client background running is draining laptop battery every couple of hours. See attached image. Additionally, since installing the client, whenever I have put the machine into sleep mode, it reboots itself within a matter of seconds of shutting the lid.

Laptop is a Dell XPS13 (9343) running Windows 10 Pro 1607 14393.1198

How is that the free version Skype screen sharing have no issues, at the same time the paid version (Teams) always have issues, even though the teams screen share is a wrapper on existing skype?

For some reason the latest update has Teams using between 8% and 25% CPU idling, doing nothing. There is an issue with this update.

Right now it simply loads too slowly, and it has that massive in-your-face splash screen while doing it.

Allow expanding just the last few comments in a thread, rather than always expanding the whole thing. A thread w/ ~200 replies takes 4-5 seconds to expand completely saturating 1 CPU core and then requires scrolling down through it all to get to the recent replies. This is particularly inconvenient if you are frequently switching channels or between Team view and Chat view as all threads are repopulated collapsed whenever you return to a channel.

We should be able to expand only the unread messages or 20 or so at a time.

Teams constantly consumes a small amount of cpu time which blocks my laptop from ever sleeping or hibernating because it is never idle. This is not ideal for many reasons. Obviously the software designed around a polling model which is not generally considered to be a great design pattern. To rephrase this as an idea: Change teams so it works on an event based model rather than constantly polling for updates.

Currently when I open a PDF in MS Teams "PDF File Viewer" I cannot click on the hyperlinks. Instead I have to download the document or open it in SharePoint just to click a link. Such a waste of time!

As the title says, our workstations which normally go to sleep after a set time now stay on forever because Microsoft Teams keeps the systems awake. Close teams, problem solved. Kind of irritating.

It can take 30s to switch between orgs/accounts in MSTeams - length of time makes the multi-org setup cumbersome to use...

scroll lag : scrolling performance (i.e. to previous messages in a chat/channel) is much worse than expected - messages don't render for a noticeable period of time

The native Mac client is very slow compared to either Slack or Hipchat when switching between channels or replying to a conversation.

Please improve the performance of the application.

Looking at UserVoice there are a few requests dealing with network utilization. Microsoft provided guidance on network bandwidth requirements for media traffic with Skype(https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/network-requirements/network-requirements). This helps provide large enteprise customers guidance during architectural decisions as well as assist with right sizing their current audio/video usage. This is missing for Team and is needed to assist customers sizing their environment correctly as well as assist with future planning. This can help decrease some of the network bandwidth asks as customers will have better guidance on what is expected with Teams over SfB