• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Intel "mesh" vs intel "Ring"

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Well - I guess we'll know when benchmarks come out of SKL-X on games (since a high proportion of clowns use these exclusively as reflective of "performance") as to how important latency is when the software, compiler and scheduler are optimised to keep threads on the same cores where possible and prefetch data where possible.
Oh actually no. What will happen is the same clowns will pick out inappropriate results from inappropriate code and use it to justify their pre-conceived idiocy.

Sure doesn't seem this way now. Some games got patched to be much more aggressive on keeping threads on one CCX, or maybe even cutting the number of threads. But both Skylake-X and Ryzen are both suffering quite a bit due to the latency.
 
im pretty sure i saw some numbers of TR having about 300ns latency when leaving the die. also intels mesh works totally different than amd's and memory speed has nothing to do with core to core latency. also low latency ram does not help core to core or ccx to ccx latency at all, only higher speeds because it raises the speed of IF as well. core to core communication does not occur through ram accesses in ANY cpu of the 2
 
Back
Top