xDiVolatilX
2[H]4U
- Joined
- Jul 24, 2021
- Messages
- 2,087
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
No, that's not really what you want to look at. It's the manufacturer and die type of the chips in question. For DDR5, I think the king is Hynix A die for Intel, and Hynix M die for AMD (well either Hynix kind of works for AMD if you're lazy). If you want to find out what type is in what (sort of), motherboard RAM support lists might give you some idea because sometimes they list manufacturer and die type.Sounds like I may need to adjust my method to look more closely at the tRAS/tRCD, but these used to not even be published in many specs. I'm glad there is more data today.
I said A BIT of a CB title to draw the watcher in (nothing wrong with that) and he then describes the concept in much more detail, which he does well. If it was all as simple as his title there would have been no need for a video now would there?How is it click bait? I've watched that video and he literally empirically shows exactly what he says in the title.
"RANT: THE CAS LATENCY TIMING DOESN'T MATTER AS MUCH AS YOU THINK IT DOES"I said A BIT of a CB title to draw the watcher in (nothing wrong with that) and he then describes the concept in much more detail, which he does well. If it was all as simple as his title there would have been no need for a video now would there?
I am legitimately trying to understand RAM speeds and timings etc. RAM tuning is complicated imo so I was looking for more answers in a discussion.This is a click-bait thread. Posting a question and then linking a video that exactly answers that question. Is this The Twilight Zone?
If it is slower in synthetics for both latency and bandwidth then it will be slower in the real world but depending on the program it just may not be a noticeable or even measurable difference.This is all good and well, but I'd like to see real world performance, not some synthetic benchmark.
For all of the timings buildzoid provided----they show the stock subtimings of the kits which they applied buildzoid's timings to. Same thing in the Intel version of the video, where they use buildzoid timings on an Intel system. I use those same timings on my Intel system, daily driving.It won't really answer your question because a lot of the benchmarked kits that have the Cas Latency as low values also have other timings at lower values, so it's hard to compare with just the claim in his video
Okay we now know your trigger words!"RANT: THE CAS LATENCY TIMING DOESN'T MATTER AS MUCH AS YOU THINK IT DOES"
This is the full title of the video. He made the video because he was actually getting annoyed with people acting like CAS Latency of their RAM kit was a big deal. He then goes on to show this empirically. Like, exactly this. Nothing else. Traditionally, clickbait involves misleading or empty titles that don't actually necessarily address their point or just don't contain any content of value. I'm not going to sit here and continue arguing semantics over this, but there is not a single thing about this video's title that I see as being clickbait except that it's in all caps (which does attract attention, because he's tired of getting the question or seeing the assertion). If that barebones minimum (title is in all caps) is your definition of clickbait, then fine I guess.
Depends on the sub timings, so no, not necessarily. Intriguing title doesn't mean clickbait.Okay we now know your trigger words!
3600CL14 is faster then 3600CL16. Ya? Buildzoid made an INTRIGING (better?) title to draw viewer in so he could explain further, ya?
I think we've seen plenty of examples of me actually getting triggered and it's a far cry from this. I'm just confused since the video title states exactly what he's going to discuss and then proceeds to discuss it lol. I guess people don't like caps...Okay we now know your trigger words!
3600CL14 is faster then 3600CL16. Ya? Buildzoid made an INTRIGING (better?) title to draw viewer in so he could explain further, ya?
I run 4 sticks of 8Gb each of DDR4- 3600. Cl 14 made by Muskin Redline,Not going to lie. I haven't bothered with RAM overclocking in a really long time.
These days I usually just shop for sticks that support the highest rated non-overclock speed in the spec of the motherboard, look for the lowest CAS timings available at that speed and go with that.
Sounds like I may need to adjust my method to look more closely at the tRAS/tRCD, but these used to not even be published in many specs. I'm glad there is more data today.
My current RAM in the Threadripper is running at the default XMP timings of DDR4-3600, 16-19-19-39 and honestly, I don't even know if that is any good
The system seems to perform OK
I feel like RAM timings are such a rabbit hole to go down that you might get lost and never return![]()
Threadripper approved
For all of the timings buildzoid provided----they show the stock subtimings of the kits which they applied buildzoid's timings to. Same thing in the Intel version of the video, where they use buildzoid timings on an Intel system. I use those same timings on my Intel system, daily driving.
View: https://youtu.be/RTmbYak_8gE?si=CQZo7PGSZiH7_o4e&t=289
I am legitimately trying to understand RAM speeds and timings etc. RAM tuning is complicated imo so I was looking for more answers in a discussion.
I've been doing these tests for years reviewing motherboards and occasionally memory modules. The thing is, CAS latencies have never meant all that much outside of synthetic testing and benchmarks. If you put two rigs side by side with the same clock speed memory, dividers, etc. you won't be able to tell a difference between them without some type of benchmark to quantify the difference. It's virtually undetectable to human perception.This is all good and well, but I'd like to see real world performance, not some synthetic benchmark.
I briefly entered the rabbit hole but it is fucking complicated me. Or maybe not so complicated, but at the very least very complex.
You have to decode things from RAM serial numbers that the manufacturers don't want you to know, in order to figure out which ram dies are on your ram sticks, and only then you have to use that information to set all of these crazy timings.
I'm still not convinced that it is actually worth the time. I'd try it, but I don't feel like looking for the serial numbers on the stickers of my RAM...
If you want to go down this rabbit hole, for DDR4 this appears to be quite the reference:
https://www.reddit.com/r/overclocking/wiki/ram/ddr4/
As is the information captured here:
https://github.com/integralfx/MemTestHelper/tree/oc-guide
But it is kind of scatter-shot, and it doesn't seem to help that the people writing many of these guides seem to have a terrible time when it comes to organizing their thoughts into written content.
This 7200 mhz kitYou use Buildzoid timings? Which kit r u using?