Ram Timing Benchmark (CL/tRCD/tRP/tRAS/CR/tRC/tRFC/tREF)

DGLee

Member
Jun 9, 2011
43
0
0
udteam.tistory.com
Hello. it's newbie on this forum.
I tested my memory with several different ram timing combinations. Tests include:
1. Super PI 32M digits of Pi calculation
2. Lavalys Everest Cache & Memory Benchmark (Bandwidth & Latency)
3. Video Encoding (1080p TP -> mkv with H.264)
Tested ram timing items are:
1. CL: 6~11
2. tRCD : 9~11
3. tRP: 6~11
4. tRAS: 24~30
5. Command Rate: 1 / 2
6. tRC: 15~40
7. tRFC: 90ns / 110ns / 160ns / 300ns / 350ns
8. tREF: 3.9ms / 7.8ms
For test of a ram timing component, other components (except tRC and tREF) are set to the lowest possible values for variable control while tRC and tREF are to have the highest possible values as default.)

System setting is as follows:
- CPU: AMD Phenom II X6 @ 4.0GHz / NB 2.75GHz
- M/B: ASUS M4A89GTD-PRO USB3
- RAM: G.SKILL PIS PC3-19200 CL9 4GB (2GB x 2) @ 2000MHz
- Storage: Intel X25-M G2 80GB
- PSU: PC Power & Cooling Silencer 910W 80PLUS Silver

Before we see the results below, I think I need to mention about the methodology used in this article: I used two different techniques to analyze the results.
First is to analyze 'numerically': calculate the ratio between 'rate of perf. change' and 'rate of ram timing value change'. It emphasizes a ram timing's theoretical contribution to performance, but not necessarily means that we could/would get those amount of perf. gain (or loss) from dealing with said ram timing component since in practice we don't always treat a ram timing as numerical value (e.g. in BIOS, we don't set 10% more to CL, 5% less to tRCD... see what I mean?)
Rather, many BIOSs provide ram timing options as up/down menu so that a user cannot accurately change the value itself but can change only the provided 'degree' (e.g. in many BIOS, for tREF, there's 3.9ms / 7.8ms / 15.6ms... and so on. There's no 4.0ms or 5.0ms. It's likely a 'degree' rather than a 'numerics'.)
So, the second method is to analyze upon 'degree change': calculate the ratio between 'rate of perf. change' and 'number of degrees change'. It is more likely what we can expect when we're dealing with a ram timing component in practice (in BIOS), but it is apart from theory.

Okay. Then we see the results!

1. Super PI
Note that among ram timing items only tRFC and tREF are indexed by 'time unit' (second) while others by clock count (how many clock cycles (= inverse time unit) are consumed for a ram timing's operation). It's because they (tRFC and tREF) directly indicate characteristics of electrical working mechanism of a memory chip. Both are related to a memory's refresh rate: tREF determines how frequently a chip shall be refreshed and tRFC determines the time elapsed between the moment of 'refresh' (memory access is unavailable) and the moment when a memory access is back to available. So in case of tREF, the bigger value implies the better performance.
617319b94b058ede96f9d14b5b21ddf3.png

53eb8d37f46d9f4d768b6c7bdf6e12aa.png

94362a8570c81cb8429b84daa57501aa.png

30e3acf4e0388b6d35a4155cca31f7eb.png

b6977ce01bb0aa523ed9c46897ae1e75.png

2afdcfc747f276d67d09937a37f321d6.png

bfe7422f5111cb7fd1784ec4aa5da185.png

375a8567a0205c969ccf82c66ca6ffb8.png


Theoretical Analysis for Super PI Test
d7780c4e7fa5bc86f78664115046a824.png

In theory, CL / tRFC / tRCD / tREF and tRAS contribute more than 1% to performance, respectively.
(Note: 4% contribution of CL means, when we change the value of CL by 10%, the performance will be affected by 10% x 4% = 0.4%)
Practical Analysis for Super PI Test
e2f76db7fa940ed208fe8245178586b5.png

In practice, tRFC and tREF seem to be important since their minimum changeable units of '1-degree' in BIOS are bigger than others. (i.e. CL's minimum unit is '1 clock counts' while tRFC's minimum unit is '20~50ns', which is equivalent to 20~50 clock counts under 1000MHz.)
 

DGLee

Member
Jun 9, 2011
43
0
0
udteam.tistory.com
3. Everest Cache & Memory Benchmark: Memory Latency
2bd5ab42414141c58455bfd56dcf11c7.png

2dbf5faba0cbb6eae597ff6937f547e9.png

813f71d76425e6c31ac0d61e07ae6871.png

bf8b0e03688dfe38f962e45742a58599.png

e6ecb5ef0cccb8950006ea91be30135d.png

8e283679b424e929e9ae9a968faa7ec0.png

af6a48c5b06d57602e89c81a48b95535.png

4e9060bd2c2c9e8a2af40c846680b58f.png


Theoretical Analysis for Latency Test
bfc4d4fe63be0a8bfced3430a2fe6083.png


Practical Analysis for Latency Test
998495cbfc6e4a3b140b08aefaa246c1.png


Latency test seems more dependant to ram timings than previous tests (Super PI & Bandwidth).
tRFC / Command Rate and CL affects similarly (around 2~2.5%) in practice.
 

DGLee

Member
Jun 9, 2011
43
0
0
udteam.tistory.com
4. Video Encoding
This test is to measure the time of converting 1920x1080 TP file to MKV, same resolution.
H.264 codec is used. No GPGPU acceleration.
e4699e67881495c25ae7a6c8cdb48940.png

85f9fa95ee5be011376fc838a47722ad.png

93c84dd9723fe8802a0e1b0079a95bcb.png

119b85ff11ee86fe047cc68bb7347bd3.png

4c53fe5bb4aacddb5393de6be383b18f.png

6c2c9e1d3cd8b6bc2f85ed9a0131e1c2.png

77eb4b2fc2f021336caf4d1aab42592e.png

cf54fc272395e3d54dfba5398c0f332f.png


Theoretical Analysis for Encoding Test
250648952f0a5ac6acf6988e6ee73d42.png


Practical Analysis for Encoding Test
e27ec10120e59d38d1de0ff48e0ad940.png


Similar to Super PI test, no ram timing affects more than 1% in practice and tREF is ranked at the highest.
 

DGLee

Member
Jun 9, 2011
43
0
0
udteam.tistory.com
So far, we covered 3 areas: Floating-point calculation, synthetic benchmark and video encoding.
Here's the graphical representation of how a ram timing affects performance through these three areas.
Theoretical Analysis
e06479225c5cd22b3110322b891ae308.png

8c10e9947164c5bd59c627eb020ca4b6.png


As you can see, CL holds the most shares in theory. tRFC and tRCD seem meaningful too.
Practical Analysis
814a7eee0fc54ceefe0d366fc2568a79.png

74046ef49c547914e7360e383b59b655.png


In practice, in addition to major shareholders in theory, Command Rate and tREF are also important.

Thanks for reading my article :)
Have a nice day~


PS. this article had also been uploaded to my blog: http://udteam.tistory.com/348 ;)