F5F Stay Refreshed Hardware Desktop MHz plus CLxx, or actual network delay

MHz plus CLxx, or actual network delay

MHz plus CLxx, or actual network delay

L
LuckySoda
Member
161
05-17-2019, 11:46 AM
#1
Consider actual performance metrics rather than just raw numbers. Compare real-world latency values—like 3600 vs. 3200 cycles per second—to see which offers better efficiency in practice.
L
LuckySoda
05-17-2019, 11:46 AM #1

Consider actual performance metrics rather than just raw numbers. Compare real-world latency values—like 3600 vs. 3200 cycles per second—to see which offers better efficiency in practice.

M
Madthunder2t3
Member
195
05-21-2019, 01:18 PM
#2
They're essentially the same. For DDR5 it's a bit different, with lower CL latency being preferable (like 5600 cl28 over 6000 cl30 or 6400 cl30). For Intel, higher speed wins (such as 7200 cl34 over 6400 cl30). I'm not entirely confident about the details, but that's what I've noticed.
M
Madthunder2t3
05-21-2019, 01:18 PM #2

They're essentially the same. For DDR5 it's a bit different, with lower CL latency being preferable (like 5600 cl28 over 6000 cl30 or 6400 cl30). For Intel, higher speed wins (such as 7200 cl34 over 6400 cl30). I'm not entirely confident about the details, but that's what I've noticed.

B
butterlover640
Junior Member
44
06-01-2019, 01:37 AM
#3
It’s much more intricate than it seems. I’ve been experimenting with memory timings over the weekend to gain a clearer picture of the problems. The chipset, memory type, and RAM all work together. I hope there’s a clearer way to describe it, but most basic explanations miss the mark because many hidden settings affect performance beyond what’s usually mentioned. There’s also the application involved. Gaming seems more affected by latency—how quickly data arrives—than by computation, which depends more on bandwidth when handling large data transfers. If the data exceeds memory caches, delays occur. Additionally, there are various memory tiers with differing speeds and sizes, similar to how GPUs handle tasks differently depending on the game or how efficiently the code manages data movement.
B
butterlover640
06-01-2019, 01:37 AM #3

It’s much more intricate than it seems. I’ve been experimenting with memory timings over the weekend to gain a clearer picture of the problems. The chipset, memory type, and RAM all work together. I hope there’s a clearer way to describe it, but most basic explanations miss the mark because many hidden settings affect performance beyond what’s usually mentioned. There’s also the application involved. Gaming seems more affected by latency—how quickly data arrives—than by computation, which depends more on bandwidth when handling large data transfers. If the data exceeds memory caches, delays occur. Additionally, there are various memory tiers with differing speeds and sizes, similar to how GPUs handle tasks differently depending on the game or how efficiently the code manages data movement.