@@fabiotiburzi Are you insane? That would effectively double the latency of a RAM chip. There's a reason as to why it's built this way - the same reason as to why UDP exists as an alternative to TCP
@@davemichael1859 Signal travel time is a miniscule part of the overall latency. The current way of blindly waiting and guessing when the memory chip might be ready doesn't sound like the best possible solution if cost were of no issue.
Bz, the task is monumental, but I'd really love for a whole series of this to be released with more complex operations than this read as pilot episode. Thank you a lot.
This kinda videos are pure Gold! I think finally starting to understand timings. If helps you to do the videos if you shorten them, please do! I will watch it multiple time probably, but shrug. Just please keep making such videos. Listen you ramble about stuff is fun, but those videos really helps me to get a better understanding wth i'm doing when tuning timings.
yeah, nobody else goes in so deep on RAM topic and at least I personally find this super interesting - probably most fascinating out of all major PC components - because there's just so much to controlling it and now I'm already convinced how dumb RAM is :D
It may be tedious and boring for you but actually understanding what exactly each timing does is very helpful! I personally would love a part 2 and would absolutely watch it
Thanks Buildzoid. Please do more of these, it's a big task trying to demystify the intricacies of memory timings but I don't think any does these explanations better
For the average pc users this wouldn't be interesting, but my guess is that everyone watching your channel really like to understand how things work and RAM is no exception.
I would definitely like to see the series continue. I learned so much from this video. You barely scratched the surface and now I want more. High Quality content.
Thanks Buildzoid! You couldn't possibly make a video that's too "tedious" for me. I love information and hardware and the pursuit of both. My next purchase is going to be a dedicated memory OC test bench and I study your content for direction. Thank you for your efforts. You will be the first person to whom I'll be a patron by year's end.
This is very useful, please continue this series. There isn't novice-friendly information on DRAM timings like this online. Especially not for secondary and tertiary timings.
Regardless if you continue to make these types of videos, this content is such valuable knowledge that isnt otherwise easily accessible. so whatever little it is worth, i appreciate it thus far.
I don’t have the words for telling you how much it helped me to understand the basic, I’ve been trying to start with overclocking, i believe this video is the foundation for every one who want to start and learn in depth the world of ram timing and overclocking, great video!
This is absolutely a project that will help so many people. If the views don't reflect that, I can bet that the people watching this will pass this information onwards
i think this will be useful to help the average Person to more understand why DRAM does matter. not just that "its important, cuz", but seeing common scenarios and seeing how much time difference there is. Video speed is appropriate for People that aren't familiar, I'd say.
Thanks for this vid! I always get confused by all the acronyms in memory timings. And which timings interact is tricky too. That cleared up a couple of things I'd misunderstood without realizing, so it was helpful for me. The pacing was appropriate to the material. Onur mutlu has some great lectures about memory on UA-cam ppl might like too. Highly recommend.
Your educational videos are my favorites and especially recently you improved my understanding of RAM a lot. But instead of overclocking, I'm more into the functionality/use of timings. So great video and I'll watch the next parts :)
It was a great explanation that clarified a lot. Like going from Command Rate 2 to 1 makes a tangible difference on tight timings, but on horribly slow timings that extra tick for each command almost completely disappears in the long waiting game.
OMG! THIS IS PERFECT! you cover this WAAAAAY better then any of the other videos i'v seen. Keep it deep in the weeds like this. I bet these videos will perform very good in the long run as people google this kind of stuff when thay start to do their first memory OCs
To answer your question - It makes sense. Please continue this series if you can. You can make future videos shorter (or longer, just quicker and with more info) because this covers the basics well.
Definitely accurate enough for people that are just trying to overclock their memory. This is definitely an accurate description of why TRAS and TRCD are not truly significant in the grand scheme of things, and their function has remained basically unchanged since the introduction of the first DRAM parts in the 1970's. They WERE quite significant in the days of fast page mode, extended data out, and SDRAM. Those memory types used much slower clocks to generate timings and had far fewer timings and operational modes for designers to concern themselves with. Very good video. A little slow for me, but I have been working with memory for a few decades.
Thanks for this Buildzoid. More for seasoned overclockers then newbies…………but we overclockers appreciate this type of in-depth insights into memory timings.
This video was long but needed. It takes this thorough breakdown to actually understand what is happening. Thank you. I would love to see more info on the other timings..
Even though I "knew" how it worked, this clarified things *A LOT* more than I expected. Using a spreadsheet for a timing diagram was honestly not something I would've thought of. Using the same method, I think I actually understand what GDM does now.
I absolutely love this! For the first time in a while I've had the clear tangible visualisation of what happens on the address level. Much appreciated!
Man this video was OUTSTANDING. Having it all broken down in tabular format, tracking the cycles and times allowed me to actually understand these timings and what they really do. Thanks BZ!
Thanks for this video! The one thing I'd suggest is adding a single sheet that has the data of all the different timings on one page to make comparisons between them easier.
Thank you! Your videos are priceless to separate marketing nonsense from what is really important to buy a decent set of RAM. Answering your question - your video does definitely makes sense and very descriptive.
Whether more people watch it or not, please make the subsequent video(s) anyway You would be the only UA-camr to have done it properly, and it's incredibly useful information I fully believe you're the only person who could pull this off while making it both accurate AND watchable. Thank you for everything you do, BZ.
I love to tinker with hardware and RAM but my brain really requires explanations like this for me to understand why a RAM OC doesn't work, and how to fix it. Hopefully this series continues.
I personally think this is great content. It provides some invaluable explanations for people who are starting to develop an interest in how RAM actually works. And this type of well explained content is hard to come by, so I hope you'll keep it up.
I found this quite informative. You speak with the knowledge of someone who clearly knows the intricacies of tuning and overclocking. I would love to see more videos on how other commands and situations work
Well, if it helps, your little hell of doing these is not in vain. At least for some of us. I love it! This is exactly what I wanted/needed! Thank you very much! I think I got the idea about the other stuff. After the read, if the read is just next column on the same row, it can immediately continue reading or something (like only sending a command and no extra waiting). If same row, but different column, then another READ with the tRCD waiting. If another row, then basically like from idle... I guess. Anyway, now it's much more clear why the CPU might have to wait more than 100 CPU cycles in order to use data from RAM, and why L1, L2, L3 sometimes even L4 exist and are important.
Well, even if you don't like to do that, this is simply one of the things i always was wondering why there wasn't any video explaining timings on your channel, thanks a lot,it is pure gold and so usefull and instructive !
I'm probably in the minority since I dont really care about overclocking, but I love the deep dives into hardware. I appreciate this video I cant imagine how much of a pain in the ass stuff like this is to make.
Please make more of these! I'm sorry they aren't fun, but they are very informative and I have a feeling the view count will age like fine wine. There aren't many resources that do a good job explaining the subject of how and why RAM works.
This was actually a pretty good explainer video. Already implies the importance of tRCD vs tCL given that i remember that "it does a lot of read bursts in a row instead of activating then reading every time" from another video (unless i remember that wrong and need to be put in my place) I would love to see them coming. Anyway you encouraged me to touch my daily settings again so let's see how that goes
This is definitely helpfull. For example I had misunderstood what CR actually does. This made it clear. I think you could leave out any idle clock cycles (just delete those rows) which would make it much easier to compare different timings and even command sequences beause you dont have to scroll.
I've been wishing to the stars for someone to properly cover memory timings in depth. While I'd hate to force you, I'll definitely be watching all of them if you do make them!
Very useful video. The explanation is clear and concise. A bit of a deeper dive would be much appreciated. You could just do a couple comparisons to shorten the video duration. What might be useful or interesting is a quick estimate on how the difference in the compared memories would affect performance.
For more complex cases it maybe easier to use timing diagrams from data sheet and calculate mark mark delays to these. This bring memories when I write SDRAM controller for cheap FPGA. I also have to say L3 to L1 caches are doing lot of work. it's pretty big delay if we need to fetch data from DDR.
Excellent information. Tip: I'd write a simple CLI script / C program to generate the data programmatically from just the timing numbers, and just print it out as CSV and import that into Excel. Same end result, but without the tedium and potential for mistakes.
My view on this may be a bit slanted as a DRAM design engineer, but I feel like the diagrams in the spec (the Micron spec you showed in the previous video has one showing this in figure 46) is way easier to look at than this spreadsheet. Time always seems easier to track on a horizontal axion s than a vertical one, and the diagrams do a good job of cutting out idle time. Other than that, great information as always, I wish I would have had videos like this when I started my career as a designer, this is way easier to understand than digging through the spec to find out what the email you were sent by your supervisor is talking about.
I hope you will cover what happens when we are reading from different bank group, it shows why having dual channel is beneficial, and why some sticks that had half bank groups were worse for performance.
Feedback: You need to only do 2-3 timings as long as for consistency you keep the speed (in this case 1.8 GHz) the same. So if you only explain timings. More would only be needed if you wanted to cover either more complicated operations and highlight the difference between 1T and 2T (if there is another difference than just keeping the command for 2 cycles vs. 1) or if you wanted to show where tighter timings don't necessarily help if the frequency is sufficiently increased - but for that you'd need to obviously abandon keeping everything at the same 3600 MT/s speed. So maybe AFTER you're done explaining memory timings ;) . 4 timings is an overkill for you and it isn't necessary. But 3 might be, just to show difference between 1T and 2T, especially if it works differently in write or more complex types of operations (dual-channel? dual rank? IDK). So far so good, the 4th timing just adds unnecessary workload to you and I'd prefer if you didn't quit making this videos just because of number of spreadsheets. Also - this works as podcast, but if you want this to be video that is only watched you don't need to read how many nanoseconds something took couple of times. We can see that. But I watch the video. IDK how many people only listen to it, so perhaps listen to their feedback first. Explaining each timing is fine, but you don't need to read out loud what is on the screen, except for the first time (so when explaining which timing is which). I don't mind it of course, but again I'd rather not have you quit, because you feel like videos are too long. This was simple operation, I assume we will be covering some more complex ones in the future. But for now I would keep to relatively simple information that are needed to explain all timings. Difference between AMD and Intel DDR4 approaches might be worthwhile, especially due to my understanding that on Zen 3 you won't exceed 1.9 GHz Infinity Fabric speed, so trying to get RAM above 3800 is worthless on Zen 3 systems, while it will be super useful on Intel ones. But this again seems like a separate topic and I only bring it up, because maybe Zen 4 will move the damn barrier somewhat. Unless all the DDR5 will have to be run on 1:2 ratio with IF. Which would be huge bottleneck, until there are good dies that can be used to make DDR5 8000. If you manage to explain timings of DDR4, then it will be much easier to explain DDR5 (I expect that demand for explaining that will rise soon, due to Zen 4 being DDR5 and Raptor Lake being last one with DDR4 support), because you will only have to explain differences. This (and previous) video was very informative and I did genuinely learn a lot from it. There isn't a single video on UA-cam that explains tertiary timings well enough, so I'm hoping for this series to continue. For now it is understandable. And while pace could be 10% faster, don't try to be super fast. RAM despite you saying it's basic, is very complicated for most users. Myself included. Thank you, from the bottom of my heart!
Really love and appreciate this. Inspired me to do a video of my timings. 5950x msi godlike pat viper steel 3333 16 20 20 20 38 @ 68ms is best I can do 51k mb/s read. Love this type of research.
I listened to this on my drive to work, and can't wait to watch it again and see the visual.. Hopefully it does you well and you'll tolerate making additional videos.. On a side note I'd love to see a video on the settings that effect memory training and improving consistency when it's seemingly on the edge
Built my first computer 2 1/2 years ago 10900k asus z4090 hero 4x8gb 17-18-18-4400mhz ram and evga rtx 3090 kingpin I knew nothing about overclocking when I built my computer but I’m still learning so much from videos like this
how and why we have RAM timings: ua-cam.com/video/105IJiGbGsg/v-deo.html
in short: because they chose the cheap way to not add a mem_active_state flag to the memory chip.
You should probably pin your comment :P
@@fabiotiburzi Are you insane? That would effectively double the latency of a RAM chip. There's a reason as to why it's built this way - the same reason as to why UDP exists as an alternative to TCP
@@davemichael1859 it depends: if a ipothetical manufacturer implement that function in a good way, the latency will not be afflict
@@davemichael1859 Signal travel time is a miniscule part of the overall latency. The current way of blindly waiting and guessing when the memory chip might be ready doesn't sound like the best possible solution if cost were of no issue.
I know you hate it, but please give us more of this. I have learned more about memory and memory timings from you, than anywhere else.
There're nowhere videos like this on UA-cam.
Big thanks for spending time on a topic that tedious
Bz, the task is monumental, but I'd really love for a whole series of this to be released with more complex operations than this read as pilot episode. Thank you a lot.
This kinda videos are pure Gold! I think finally starting to understand timings. If helps you to do the videos if you shorten them, please do! I will watch it multiple time probably, but shrug. Just please keep making such videos. Listen you ramble about stuff is fun, but those videos really helps me to get a better understanding wth i'm doing when tuning timings.
yeah, nobody else goes in so deep on RAM topic and at least I personally find this super interesting - probably most fascinating out of all major PC components - because there's just so much to controlling it and now I'm already convinced how dumb RAM is :D
Thanks!
It might be boring for you, but it's exciting for those who are new to tuning RAM.
Literally this. All I knew before is lower numbers is better but not why.
It may be tedious and boring for you but actually understanding what exactly each timing does is very helpful! I personally would love a part 2 and would absolutely watch it
Thanks Buildzoid. Please do more of these, it's a big task trying to demystify the intricacies of memory timings but I don't think any does these explanations better
For the average pc users this wouldn't be interesting, but my guess is that everyone watching your channel really like to understand how things work and RAM is no exception.
I would definitely like to see the series continue. I learned so much from this video. You barely scratched the surface and now I want more. High Quality content.
Agree you can do with just two sets of timings. Do a good and a crappy one. And I'm putting my money where my mouth is: I WANT TO KNOW, MMMKAY?
Been waiting for this one!
Buildzoid gives so many unmotivated professor vibes. I love it
Thanks Buildzoid! You couldn't possibly make a video that's too "tedious" for me. I love information and hardware and the pursuit of both. My next purchase is going to be a dedicated memory OC test bench and I study your content for direction. Thank you for your efforts. You will be the first person to whom I'll be a patron by year's end.
13:04 and this is why we love you and your work
This is very useful, please continue this series. There isn't novice-friendly information on DRAM timings like this online. Especially not for secondary and tertiary timings.
True. And I would like to learn more.
+1 here
This is your best content, man. Keep the next one going!
Regardless if you continue to make these types of videos, this content is such valuable knowledge that isnt otherwise easily accessible. so whatever little it is worth, i appreciate it thus far.
I don’t have the words for telling you how much it helped me to understand the basic, I’ve been trying to start with overclocking, i believe this video is the foundation for every one who want to start and learn in depth the world of ram timing and overclocking, great video!
I've had so much trouble finding DDR4 timing diagrams to understand what the timings do, this is a goldmine worth of information! Thank you so much!
This is absolutely a project that will help so many people. If the views don't reflect that, I can bet that the people watching this will pass this information onwards
i think this will be useful to help the average Person to more understand why DRAM does matter.
not just that "its important, cuz", but seeing common scenarios and seeing how much time difference there is.
Video speed is appropriate for People that aren't familiar, I'd say.
Thanks for this vid! I always get confused by all the acronyms in memory timings. And which timings interact is tricky too.
That cleared up a couple of things I'd misunderstood without realizing, so it was helpful for me. The pacing was appropriate to the material.
Onur mutlu has some great lectures about memory on UA-cam ppl might like too. Highly recommend.
Your educational videos are my favorites and especially recently you improved my understanding of RAM a lot. But instead of overclocking, I'm more into the functionality/use of timings. So great video and I'll watch the next parts :)
It was a great explanation that clarified a lot. Like going from Command Rate 2 to 1 makes a tangible difference on tight timings, but on horribly slow timings that extra tick for each command almost completely disappears in the long waiting game.
Please continue with this series.
Thank you for this, Zoid! Really very much appreciated. 🍻
This half-hour video flew away like it was 5min!
You are doing a favour to the entire community with these awesome (but tedious for you) videos
Looking forward to future episodes
BZ, you're the only person I know making content like this. Please continue this series! This is top tier stuff!
OMG! THIS IS PERFECT! you cover this WAAAAAY better then any of the other videos i'v seen. Keep it deep in the weeds like this. I bet these videos will perform very good in the long run as people google this kind of stuff when thay start to do their first memory OCs
Buildzoid i love your passively aggressive explanation. Exactly the right pace.
To answer your question - It makes sense. Please continue this series if you can. You can make future videos shorter (or longer, just quicker and with more info) because this covers the basics well.
This is good stuff, I hope you continue this series.
Definitely accurate enough for people that are just trying to overclock their memory. This is definitely an accurate description of why TRAS and TRCD are not truly significant in the grand scheme of things, and their function has remained basically unchanged since the introduction of the first DRAM parts in the 1970's. They WERE quite significant in the days of fast page mode, extended data out, and SDRAM. Those memory types used much slower clocks to generate timings and had far fewer timings and operational modes for designers to concern themselves with.
Very good video. A little slow for me, but I have been working with memory for a few decades.
I appreciate explanation videos like these, they help beginners like myself understand how this all works, great content!
Thanks for this Buildzoid. More for seasoned overclockers then newbies…………but we overclockers appreciate this type of in-depth insights into memory timings.
"yay me, I hate this, I hate this so much" - thank you @buildzoid for taking the time to do this.
This video was long but needed. It takes this thorough breakdown to actually understand what is happening. Thank you. I would love to see more info on the other timings..
Bz, many thanks for stuff like this. This is absolutely gorgeous explanation of what's going on in RAM. Please do more!!!
I think there's no such content on youtube. I've searched for some explanation like this for ages, thank you.
Even though I "knew" how it worked, this clarified things *A LOT* more than I expected. Using a spreadsheet for a timing diagram was honestly not something I would've thought of.
Using the same method, I think I actually understand what GDM does now.
I absolutely love this! For the first time in a while I've had the clear tangible visualisation of what happens on the address level. Much appreciated!
Man this video was OUTSTANDING. Having it all broken down in tabular format, tracking the cycles and times allowed me to actually understand these timings and what they really do. Thanks BZ!
Thanks for this video! The one thing I'd suggest is adding a single sheet that has the data of all the different timings on one page to make comparisons between them easier.
Thank you! Your videos are priceless to separate marketing nonsense from what is really important to buy a decent set of RAM. Answering your question - your video does definitely makes sense and very descriptive.
These kinds of videos are non existent on the platform. Really needed
Commenting to boost engagement and tell you we appreciate it immensely!
I am new to DDR, love this training series instead of me reading the datasheet myself. Thank you!
I went back and watched the recommended video first. I've learnt a lot from both, so thank you for making them.
awesome breakdown cant wait for part 2
Whether more people watch it or not, please make the subsequent video(s) anyway
You would be the only UA-camr to have done it properly, and it's incredibly useful information
I fully believe you're the only person who could pull this off while making it both accurate AND watchable.
Thank you for everything you do, BZ.
I love to tinker with hardware and RAM but my brain really requires explanations like this for me to understand why a RAM OC doesn't work, and how to fix it. Hopefully this series continues.
I personally think this is great content. It provides some invaluable explanations for people who are starting to develop an interest in how RAM actually works. And this type of well explained content is hard to come by, so I hope you'll keep it up.
Thank you for doing this Mr Zoid. I dont believe anyone in recent times has done this type of instructional. Well done Sir.
I found this quite informative. You speak with the knowledge of someone who clearly knows the intricacies of tuning and overclocking. I would love to see more videos on how other commands and situations work
Well, if it helps, your little hell of doing these is not in vain. At least for some of us. I love it! This is exactly what I wanted/needed! Thank you very much!
I think I got the idea about the other stuff. After the read, if the read is just next column on the same row, it can immediately continue reading or something (like only sending a command and no extra waiting). If same row, but different column, then another READ with the tRCD waiting. If another row, then basically like from idle... I guess.
Anyway, now it's much more clear why the CPU might have to wait more than 100 CPU cycles in order to use data from RAM, and why L1, L2, L3 sometimes even L4 exist and are important.
Well, even if you don't like to do that, this is simply one of the things i always was wondering why there wasn't any video explaining timings on your channel, thanks a lot,it is pure gold and so usefull and instructive !
This was a fantastic explanation. Thanks so much for taking the time to explain this, really well done!
Please please do an ep 2. Been a sub of yours for many years and I feel the community would really appreciate this.
Thank you for making the rest of the parts. I've learned a lot from these.
its my birthday and Buildzoid treated me with this, love your content
Thank you so much. If it wasn't for this video, I would be in an infinite loop of searching for ddr4 operations in Internet.
I'm probably in the minority since I dont really care about overclocking, but I love the deep dives into hardware. I appreciate this video I cant imagine how much of a pain in the ass stuff like this is to make.
Sweet! While I don't watch everything you post this is what I needed to understand ram.
Please make more of these! I'm sorry they aren't fun, but they are very informative and I have a feeling the view count will age like fine wine. There aren't many resources that do a good job explaining the subject of how and why RAM works.
This was actually a pretty good explainer video. Already implies the importance of tRCD vs tCL given that i remember that "it does a lot of read bursts in a row instead of activating then reading every time" from another video (unless i remember that wrong and need to be put in my place) I would love to see them coming. Anyway you encouraged me to touch my daily settings again so let's see how that goes
This is definitely helpfull. For example I had misunderstood what CR actually does. This made it clear.
I think you could leave out any idle clock cycles (just delete those rows) which would make it much easier to compare different timings and even command sequences beause you dont have to scroll.
Appreciate the effort that went into this. For the first time I finally understand what these timings actually mean.
Thanks!
I've been wishing to the stars for someone to properly cover memory timings in depth. While I'd hate to force you, I'll definitely be watching all of them if you do make them!
This is a very informative video. I'd love to see a part 2 and more if possible! :)
THE NUMBERS MASON! WHAT DO THEY MEAN?
-I love that content! Thank you very much and keep on with that excellent work!
Very useful video. The explanation is clear and concise. A bit of a deeper dive would be much appreciated.
You could just do a couple comparisons to shorten the video duration.
What might be useful or interesting is a quick estimate on how the difference in the compared memories would affect performance.
I've learned so much watching this video series about something that's been a great mistery to me all these years lol
wow I feel like waiting for my lifetime for this info come. pls keep it pls
This was excellent! I have a much, much, much better understanding of this whole thing.
I sincerely hope this series winds up being your most popular videos lol
thank you for time and expertise on subject matter way above most normal people
For more complex cases it maybe easier to use timing diagrams from data sheet and calculate mark mark delays to these.
This bring memories when I write SDRAM controller for cheap FPGA.
I also have to say L3 to L1 caches are doing lot of work. it's pretty big delay if we need to fetch data from DDR.
Excellent information. Tip: I'd write a simple CLI script / C program to generate the data programmatically from just the timing numbers, and just print it out as CSV and import that into Excel. Same end result, but without the tedium and potential for mistakes.
Highly appreciate this content
My view on this may be a bit slanted as a DRAM design engineer, but I feel like the diagrams in the spec (the Micron spec you showed in the previous video has one showing this in figure 46) is way easier to look at than this spreadsheet. Time always seems easier to track on a horizontal axion s than a vertical one, and the diagrams do a good job of cutting out idle time.
Other than that, great information as always, I wish I would have had videos like this when I started my career as a designer, this is way easier to understand than digging through the spec to find out what the email you were sent by your supervisor is talking about.
Some of the later access patterns I want to show will have pretty much 0 idle time on the DQ and the spreadsheet is a pretty fast way of making these
Awesome video, I'm looking forward to the continuation.
Thank you for this. You're doing gods work.
Good stuff!
Make more of these no one actually teaches DDR tuning
I hope you will cover what happens when we are reading from different bank group, it shows why having dual channel is beneficial, and why some sticks that had half bank groups were worse for performance.
Simple, clear and to the point. Nicely done.
thanks for the effort explaining this BZ, really appreciated
gives me a basic idea how it works ^^
Thank you putting in the time for our puny minds even if its painful!
I'm learning alot here. I didn't realize all operations happened in a specific order.
Really learnt something, looking forward to part 2.
Feedback: You need to only do 2-3 timings as long as for consistency you keep the speed (in this case 1.8 GHz) the same. So if you only explain timings. More would only be needed if you wanted to cover either more complicated operations and highlight the difference between 1T and 2T (if there is another difference than just keeping the command for 2 cycles vs. 1) or if you wanted to show where tighter timings don't necessarily help if the frequency is sufficiently increased - but for that you'd need to obviously abandon keeping everything at the same 3600 MT/s speed. So maybe AFTER you're done explaining memory timings ;) . 4 timings is an overkill for you and it isn't necessary. But 3 might be, just to show difference between 1T and 2T, especially if it works differently in write or more complex types of operations (dual-channel? dual rank? IDK). So far so good, the 4th timing just adds unnecessary workload to you and I'd prefer if you didn't quit making this videos just because of number of spreadsheets.
Also - this works as podcast, but if you want this to be video that is only watched you don't need to read how many nanoseconds something took couple of times. We can see that. But I watch the video. IDK how many people only listen to it, so perhaps listen to their feedback first. Explaining each timing is fine, but you don't need to read out loud what is on the screen, except for the first time (so when explaining which timing is which). I don't mind it of course, but again I'd rather not have you quit, because you feel like videos are too long. This was simple operation, I assume we will be covering some more complex ones in the future. But for now I would keep to relatively simple information that are needed to explain all timings.
Difference between AMD and Intel DDR4 approaches might be worthwhile, especially due to my understanding that on Zen 3 you won't exceed 1.9 GHz Infinity Fabric speed, so trying to get RAM above 3800 is worthless on Zen 3 systems, while it will be super useful on Intel ones. But this again seems like a separate topic and I only bring it up, because maybe Zen 4 will move the damn barrier somewhat. Unless all the DDR5 will have to be run on 1:2 ratio with IF. Which would be huge bottleneck, until there are good dies that can be used to make DDR5 8000.
If you manage to explain timings of DDR4, then it will be much easier to explain DDR5 (I expect that demand for explaining that will rise soon, due to Zen 4 being DDR5 and Raptor Lake being last one with DDR4 support), because you will only have to explain differences.
This (and previous) video was very informative and I did genuinely learn a lot from it. There isn't a single video on UA-cam that explains tertiary timings well enough, so I'm hoping for this series to continue. For now it is understandable. And while pace could be 10% faster, don't try to be super fast. RAM despite you saying it's basic, is very complicated for most users. Myself included.
Thank you, from the bottom of my heart!
This was very informative. I definitely appreciated the breakdown.
You've explained it and set out the detail very well. Thanks!
Really love and appreciate this. Inspired me to do a video of my timings. 5950x msi godlike pat viper steel 3333 16 20 20 20 38 @ 68ms is best I can do 51k mb/s read. Love this type of research.
I like the content and i like the way you expose it, so please continue!
Just a comment to help with the algorithm. Good stuff, I'm learning a lot from it so thank you.
Wonderful. I'm starting to understand what is behind the timing values.
I listened to this on my drive to work, and can't wait to watch it again and see the visual.. Hopefully it does you well and you'll tolerate making additional videos..
On a side note I'd love to see a video on the settings that effect memory training and improving consistency when it's seemingly on the edge
Built my first computer 2 1/2 years ago 10900k asus z4090 hero 4x8gb 17-18-18-4400mhz ram and evga rtx 3090 kingpin I knew nothing about overclocking when I built my computer but I’m still learning so much from videos like this