Comment by dijit
18 hours ago
There's something weird going on honestly.
On an i9-14900K, arguably one of the fastest CPUs in the previous few years (and excusing their design defect that causes them to die); Teams is significantly slower than on the Quallcom Snapdragon X-Elite, or my Macbook.
It seems to perform the same as it would on an i9 platform as it does on i5 laptop's of the same generation (in terms of input latency and drawing to the screen etc;)
I know it's apples/oranges, that ARM CPUs are substantially different than x86 ones, but the fact that it seems to be the same on significantly lower clocked (and lower consumptive) chips indicate to me that something very bizarre is happening when it comes to Teams.
ARM chips seem to be significantly better for electron applications, but something unique exists within Teams here.
Hypothesis: that Qualcomm and that Macbook have higher memory bandwidth than your i9 system. This is dependent on your memory and your mainboard, not so much on the CPU itself. Perhaps Teams just uses way too much memory, and actually uses it all the time.
I mean dude said he's doing multitaskign stuff --in-- teams and it's slow.
To me memory latency being whatever, 30% higher, ought not to explain the issue here, in part because that's a priori assuming all is memory-bandwidth-limited vs say network limited or CPU limited far as the bottleneck
What makes more sense to me is the software is "slow and clunky" that is maybe a global mutex, maybe poor multithreading sync making it effectively single threaded, with a sprinkling of particularly slow algorithms or syscalls that are realized as a frozen GUI, or as we call such cases, Microsoft standard
That is an interesting hypothesis, and makes sense based on the generationality of the issue.
An i5-14500 has a comparable memory bandwidth as an i9-14900k
https://www.intel.com/content/www/us/en/products/compare.htm...
No idea, but I have found that edge can be more conservative in its use of GPU acceleration than Chrome. Maybe that is the case in the webview Teams uses.