HWBOT Memory Index v0.1

  • News, Editorials, Articles
  • 9

Author: Pieter-Jan Plaisier


It’s been a while since HWBOT hosted a proper research article. This mostly due to a pile of other work preventing me from digging into anything in-depth. Luckily, I’ve managed to find a small opening in the schedule to wrap this article up.

Everyone knows that the HWBOT database is filled with benchmark results, overclocking data and so much more. One of the perks of having a database like this is not only to amuse (and annoy) overclockers globally, but mainly to analyze the results afterwards and have a better understanding of how the overclocking game really works. Processor and video card charts are scattered around the website, but memory overclocking charts is something we haven’t touched before.

Although that last sentence was one of the reasons why I wanted to dig into the data we have on memory overclocking, it’s certainly not the most important one. I know, I know, some people see HWBOT as yet-another marketing website, but those who really understand what we do and how we look at marketing will know that the opposite is true. So, the main reason why I wanted to make memory recommendation charts is because I’m getting more and more fed up by the latest trend to use abnormally high timings and enabling B2B-Cas Delay for high frequency CPU-Z suicide shots and using those shots as some kind of proof that this memory kit is in fact the best you can get. No, people, no … DDR3-3000 CL10-15-10 B2B=31 is not the best you can get.

The Charts

For those who don’t want the explanation and logic behind the charts, we’ve placed them on the first page of the article. For those who want to understand how these charts were build up, continue the long read.

<< Page 2 – Methodology and further explanations >>


Belgium Massman says:

While writing the article, I realized that there's still so much to research and add to this article. Normally this would've been a v1, but because of the (in my opinion) shortage of data, I've made it a v0.1.

Nevertheless, it's an example of the route we'll be taking for memory charts.

Let me know your thoughts!

Switzerland Christian Ney says:


TaPaKaH says:

second chart, A-Data 80.2 is under Diablo 80.15

Belgium Massman says:

I've updated the chart + corrected link to page 2 :)

United States Voidn says:

Mmmm data. :thumbup:

Iran siavash_shojaee says:

tanx :-)

United States Hondacity says:

how do we generated the index? thru maxmem results? memory clock results?


HWBOT Memory Index = a x Avg(MHz) / [ (b x Avg(tCL)) + (c x Avg(tRCD))]

The second page has all the methodology that was used. :)

Belgium Massman says:

I hope to get the tests for the Clarkdale and Lynnfield processors done this week. I'll be adding the charts to the first page then. After that: mainboard rankings :)

Please log in or register to comment.