Do RAM Timings Really Matter for Software Development?

Interestingly, some systems, like those from Puget Systems, use RAM with higher timings (CL46). It's worth noting that for many applications, what you prioritize may differ between different setups and needs.

Actually, RAM timings can affect performance in some scenarios, especially when dealing with heavy workloads like compiling or intensive applications. Lower timings (like CL30) can mean quicker data access, which is helpful. But remember, having enough RAM (16GB or more) is usually more critical than obsessing over timings. Once you've got that covered, faster RAM can definitely make your tools feel more responsive!

Generally, RAM timings might not make a huge difference in day-to-day software development. For tasks like compiling large projects or running multiple VMs, lower latency could help a bit, but it's probably not worth spending twice as much on faster timings. Focus on ensuring you have enough RAM first.

Consider your SSD speed too! If your SSD is slow, it could bottleneck your entire workflow, making RAM timings less important. In ML tasks, if your models fit into GPU memory, RAM isn't even a factor. But if not, it can become relevant as data swaps in and out.