Jump to content

Zen+ latency penalty over 2933MHz RAM?

Go to solution Solved by Sakkura,

Zen+ (and original Zen) doesn't have that DRAM:IF decoupling feature, so this behavior doesn't exist. However, instead it just can't run with as fast memory as Zen 2. DDR4-3200 is about as much as you can really count on, beyond that it gets more and more tricky.

Hello, I’ve been wondering if there’s such graph for zen+ processors showing latency penalty over 2933MHz RAM or 3200, basically decoupling from the infinity fabrics?

I don’t know if I should keep my 3400cl16 or go with 3200cl14 on Ryzen 5 2600

A6EBB1A9-7050-40D3-BC01-7BDC35A42EE4.jpeg

Link to comment
Share on other sites

Link to post
Share on other sites

Zen+ (and original Zen) doesn't have that DRAM:IF decoupling feature, so this behavior doesn't exist. However, instead it just can't run with as fast memory as Zen 2. DDR4-3200 is about as much as you can really count on, beyond that it gets more and more tricky.

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, Sakkura said:

Zen+ (and original Zen) doesn't have that DRAM:IF decoupling feature, so this behavior doesn't exist. However, instead it just can't run with as fast memory as Zen 2. DDR4-3200 is about as much as you can really count on, beyond that it gets more and more tricky.

I mean I’m running 3400CL16 at the minute, but CPU-Z shows like 3:53 FSB:DRAM i think so that’s why I’m asking. Are you sure that it’s not existing? I think it should be 1:1 then?

Link to comment
Share on other sites

Link to post
Share on other sites

15 minutes ago, uberas said:

I mean I’m running 3400CL16 at the minute, but CPU-Z shows like 3:53 FSB:DRAM i think so that’s why I’m asking. Are you sure that it’s not existing? I think it should be 1:1 then?

FSB:DRAM is a different thing from Fclk:Uclk (fabric and memory controller clocks).

 

The FSB name is kind of a leftover from a bygone era. It doesn't mean much today. Anyway, I believe it's defined to be 2x the base-clock on Zen+, ie. 200 MHz. 200:3400 then for some reason ends up simplified to 3:53 (it ought to be 3:51, or even better 1:17).

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, Sakkura said:

FSB:DRAM is a different thing from Fclk:Uclk (fabric and memory controller clocks).

 

The FSB name is kind of a leftover from a bygone era. It doesn't mean much today. Anyway, I believe it's defined to be 2x the base-clock on Zen+, ie. 200 MHz. 200:3400 then for some reason ends up simplified to 3:53 (it ought to be 3:51, or even better 1:17).

Okay, I’ll try to jump my memory to 3733CL16 then if sky’s the limit. Thanks for help 

Link to comment
Share on other sites

Link to post
Share on other sites

5 hours ago, uberas said:

Okay, I’ll try to jump my memory to 3733CL16 then if sky’s the limit. Thanks for help 

Most likely 3600MHz 14-15-14-14 is going to be where reliability stops.  I can get some boots with good memory training "stable" at 3666MHz and 3733Mhz.  

 

I run these timings as my daily with 1.48V on DRAM and SOC at 1.00V.  

 

You're gonna need that 3200CL14 b-die kit or better for it though.  

Daily.png

AMD Ryzen 5800XFractal Design S36 360 AIO w/6 Corsair SP120L fans  |  Asus Crosshair VII WiFi X470  |  G.SKILL TridentZ 4400CL19 2x8GB @ 3800MHz 14-14-14-14-30  |  EVGA 3080 FTW3 Hybrid  |  Samsung 970 EVO M.2 NVMe 500GB - Boot Drive  |  Samsung 850 EVO SSD 1TB - Game Drive  |  Seagate 1TB HDD - Media Drive  |  EVGA 650 G3 PSU | Thermaltake Core P3 Case 

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×