Microsoft
MicrosoftIt is great to hear such a stories, peace by peace you could improve the Teams. Have you though about to put these on the road map? As currently, my Teams eats 1,1 GB RAM, when it does nothing, just sitting on background. So should I expect that I do not have the improvements applied to my version 1.4.00.35564, or are these coming. Obviously the numbers change when I activate that, and e.g. CPU load gets surprising high when I just typing the message to my colleague (not sent). When having Teams on VDI platform, all improvements matters.
Reason to ask making these more visible (roadmap) is, as many of us on these forums are saying, it is super hard to us to put any expectations to Teams quality when we do not have knowledge when changes has been applied to us. The changes like these should be easy to announce: "In version 1.4.xxxxx memory optimization has been applied."
But one one thing you really should focus is: "dirty data in cache". It is very hard to understand that you are not able to detect when Teams' cache (or part of it) has become corrupted/unavailable. Just too often the solution is "clear the cache", no matter what kind troubles you do have on Teams, that is the solution.
As a solution different companies has build own scripts for users to launch to clear the cache, or others has asked to get a button [Clear Cache] into Teams. I still believe (and hope) that you could build a Cache Health Check into Teams, which knows when cache can be wiped and fresh data need to be downloaded. Isn't that the correct way to fix it? Don't propose feedback site, I have only two votes to that 😄
