4 ms·

RAM signalization is very sensitive to data line length, more so if you use low power RAM modules. This is not a "bigger number in a useless benchmark" thing,

RAM signalization is very sensitive to data line length, more so if you use low power RAM modules. This is not a "bigger number in a useless benchmark" thing, if you can standardize the shortest and fastest routing possible with a socket, everybody can use faster RAM for less (RAM command waits are the biggest killer of responsiveness), and everyone can enjoy faster, more responsive systems. Moreover, bigger RAM means bigger caches in any OS, and having these caches on faster storage means snappier, faster systems. Lastly, games and other engineering software use great amounts of RAM and moves tons of data between GPU RAM and system RAM. Having faster pipes helps. It's not about benchmarks, it's about real world performance.

nottorp 2y ago
Is it? They're preventing you from having more ram in the name of having a limited amount of ram that is faster. Which, as you said yourself, is useless if your working set doesn't fit in your limited amount of ram. > RAM command waits are the biggest killer of responsiveness ... no, using swap is the biggest killer of responsiveness :)
- bayindirh 2y ago
  I'm looking some of the latest Intel processors' specifications: - Intel Core Ultra 9 185H: 2 memory channels. - Intel Core Ultra 7 165U: 2 memory channels. - Intel Core i9-14900KF: 2 memory channels. The last one is a 6GHz, 24 core, 32 thread, 253W behemoth, and even that has two memory channels. What's the benefit of having four slots, and adding more wait states and reducing bandwidth in a system this powerful? That doesn't make sense. Instead, I'd rather have two channels in a module, and change the whole RAM in one swoop. If you are unsure, over-speccing a system slightly at the start won't hurt on the long run. > using swap is the biggest killer of responsiveness I have bad news for you, then. Even if you have tons of free RAM, unused pages are still pushed to your swap. On the other hand, while swap heavy computation is a last-resort in high load systems, command waits are with you the moment you touch your power button.
  - nottorp 2y ago
    > If you are unsure, over-speccing a system slightly at the start won't hurt on the long run. Hey, this is what the Apple haters are complaining about :) Seems to be coming on Wintel too. > unused pages are still pushed to your swap On Windows? Pretty sure that both on Mac OS and Linux I can have the swap mostly unused. Or even run without swap on Linux.
    - bayindirh 2y ago
      > On Windows? Pretty sure that both on Mac OS and Linux I can have the swap mostly unused. Nope, on Linux. My macOS system is not using its swap at the moment, but I saw it's using it when both memory pressure was low and there was free space. OTOH, on my 32GB Linux system, current state is as follows: total used free shared buff/cache available Mem: 31894 10051 2967 169 19498 21843 Swap: 15722 2506 13216 This is system has not been stressed to full RAM since last boot. It's Linux kernel's own choice to move these pages to swap over time. > Or even run without swap on Linux. This is how Kubernetes systems and most HPC clusters run, and hard-lock the moment you hit 0 on "free" column.

nottorp 2y ago

Is it? They're preventing you from having more ram in the name of having a limited amount of ram that is faster. Which, as you said yourself, is useless if your working set doesn't fit in your limited amount of ram. > RAM command waits are the biggest killer of responsiveness ... no, using swap is the biggest killer of responsiveness :)

bayindirh 2y ago
I'm looking some of the latest Intel processors' specifications: - Intel Core Ultra 9 185H: 2 memory channels. - Intel Core Ultra 7 165U: 2 memory channels. - Intel Core i9-14900KF: 2 memory channels. The last one is a 6GHz, 24 core, 32 thread, 253W behemoth, and even that has two memory channels. What's the benefit of having four slots, and adding more wait states and reducing bandwidth in a system this powerful? That doesn't make sense. Instead, I'd rather have two channels in a module, and change the whole RAM in one swoop. If you are unsure, over-speccing a system slightly at the start won't hurt on the long run. > using swap is the biggest killer of responsiveness I have bad news for you, then. Even if you have tons of free RAM, unused pages are still pushed to your swap. On the other hand, while swap heavy computation is a last-resort in high load systems, command waits are with you the moment you touch your power button.
- nottorp 2y ago
  > If you are unsure, over-speccing a system slightly at the start won't hurt on the long run. Hey, this is what the Apple haters are complaining about :) Seems to be coming on Wintel too. > unused pages are still pushed to your swap On Windows? Pretty sure that both on Mac OS and Linux I can have the swap mostly unused. Or even run without swap on Linux.
  - bayindirh 2y ago
    > On Windows? Pretty sure that both on Mac OS and Linux I can have the swap mostly unused. Nope, on Linux. My macOS system is not using its swap at the moment, but I saw it's using it when both memory pressure was low and there was free space. OTOH, on my 32GB Linux system, current state is as follows: total used free shared buff/cache available Mem: 31894 10051 2967 169 19498 21843 Swap: 15722 2506 13216 This is system has not been stressed to full RAM since last boot. It's Linux kernel's own choice to move these pages to swap over time. > Or even run without swap on Linux. This is how Kubernetes systems and most HPC clusters run, and hard-lock the moment you hit 0 on "free" column.