zlacker

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.

>>tomsme+(OP)
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...

>>tomsme+(OP)
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

>>amypet+aB1
but a sprinkling of singleton’s/mutex’s would indeed be less painful with higher memory bandwidths and latencies.